Skip to content

docs: archive the skip-unreleased-package OpenSpec change - #206

Merged
any-victor merged 3 commits into
mainfrom
chore/archive-skip-unreleased
Oct 22, 2026
Merged

any-victor merged 3 commits into
mainfrom
chore/archive-skip-unreleased

Conversation

@any-victor

@any-victor any-victor commented Oct 22, 2026 •

Copy link
Copy Markdown
Contributor

verctl 0.5.4 shipped #204, so this archives its OpenSpec change. The release-plan requirement moves to openspec/specs/release-plan/spec.md, the tasks carry their CI evidence, and VER-077 moves to the archive with its evidence.

It also archives VER-069. #174 completed it on 2026-10-18, so mise run q check failed on main until now. The one open proof, task 2.4 of cargo-workspace-publish, moves to the new row VER-078: a code review of registry_lists and released_crates, then the first workspace release reporting each member. That change stays unarchived until 2.4 closes.

verctl 0.5.4 shipped it, so its release-plan requirement moves to
openspec/specs/release-plan/spec.md and VER-077 moves to the archive.

Completes: VER-077
@kodus-hostinger

kodus-hostinger Bot commented Oct 22, 2026 •

Copy link
Copy Markdown

Review

Incremental · 0 open

@kody review after new commits. @kody full re-reads the whole PR.

Summary

This pass closes out the cargo workspace publishing work (VER-069) in the task tracker. The one proof step still open moves to a new follow-up row, so the OpenSpec change stays open until that step is done.

Task tracker (tasks.yaml)

  • VER-069 archived: "Publish a cargo workspace one member at a time" moves from the queue to the archive.
    • It is marked completed (2026-10-22), with disposition: completed.
    • The evidence points to feat: publish a cargo workspace one member at a time (VER-069) #174 (commit b9c9f3d, 2026-10-18) as the change that implemented it.
    • The original notes are kept, including the orchestrator decision to implement this in verctl instead of a per-repository publish task.
    • The evidence also states that the remaining proof moves to VER-078.
  • VER-078 added to the queue: "A workspace release proves member-complete pending and docs."
    • Scope: src/pending.rs, src/registry.rs, src/docsrs.rs.
    • Purpose: show that pending treats a workspace package as complete only when every member is listed, and that docs waits for every library member.
    • Acceptance: a code review of registry_lists and released_crates confirms both rules, and the first workspace release reports each member.
    • Links: it points to openspec/changes/cargo-workspace-publish/proposal.md as its plan, and notes that it covers only task 2.4.

OpenSpec change (openspec/changes/cargo-workspace-publish/tasks.md)

  • Task 2.4 stays unchecked. A dated note (2026-10-22) says:
    • it is tracked by VER-078 until the first workspace release;
    • VER-069 is archived;
    • the OpenSpec change stays open until 2.4 closes.

No source code changes are included; this pass only updates task tracking and documentation.

Files

File Status + −
openspec/changes/cargo-workspace-publish/tasks.md modified +1 −0
tasks.yaml modified +28 −14

Open

No open findings.

History

When Pass Open
22 Oct 07:02 UTC Incremental 0
22 Oct 07:00 UTC Full 0
22 Oct 06:55 UTC Incremental 1
22 Oct 06:52 UTC Incremental 0

Inspect this review

Comment thread tasks.yaml
The archive left a TBD purpose without a blank line below its heading,
which lint:md rejects.
@any-victor
any-victor force-pushed the chore/archive-skip-unreleased branch from ea75c29 to dbf5fd3 Compare October 22, 2026 07:00
#174 completed VER-069 on 2026-10-18, so q check required its archive.
Task 2.4 of cargo-workspace-publish still waits for the first workspace
release, so VER-078 tracks that proof and the change stays open.
@any-victor
any-victor merged commit 58d08cd into main Oct 22, 2026
4 checks passed
@any-victor
any-victor deleted the chore/archive-skip-unreleased branch October 22, 2026 07:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant