Repository navigation
fix(publish): leave a package at 0.0.0 out of the release plan - #204
Merged
Merged
Conversation
A crate that adopted the release workflow at 0.0.0 had its placeholder planned as a release. No registry lists 0.0.0, so publish --plan named the commit where 0.0.0 first appeared, and every push to the default branch failed before the Version PR job. pending now skips a 0.0.0 package before any lookup, and publish asks no changelog section of it. bump::apply and pending share one test for an unreleased version.
ReviewIncremental · 0 open
SummaryThis pass updates only the task checklist for the Tasks marked completeEach of these tasks is now checked off and cites the passing CI result from verify run 39726352572:
New task added
Still open
Files
OpenNo open findings. History
|
With the shared v{version} template, a new package at 0.0.0 beside a
released one made plan refuse differing versions. plan now renders
tags over released packages only, and a dry run leaves the new package
out, as publish does.
A dry run whose packages are all at 0.0.0 now reports the same outcome as publish, instead of an empty plan.
vsh-changeset-version Bot
added a commit
that referenced
this pull request
Oct 22, 2026
## verctl 0.5.4
- `verctl publish --plan` and `verctl publish` leave out a package at `0.0.0`, before any registry or GitHub lookup, `publish` asks no changelog section of it, and it gets no tag, so a new package beside a released one no longer breaks a shared `v{version}` tag. A crate that adopted the release workflow at `0.0.0` had its placeholder planned as a release, so every push to its default branch ran the publish job on the commit where `0.0.0` first appeared, and the Version PR job never ran ([#204](#204)).
any-victor
added a commit
that referenced
this pull request
Oct 22, 2026
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
A new package starts at
0.0.0and releases0.0.1first, butpublish --planplanned the placeholder: no registry lists0.0.0.A crate that adopted the reusable release workflow at
0.0.0failed every push to its default branch.The plan named the commit where
0.0.0first appeared, which predates thevertask, so the publish and docs.rs jobs failed withno task ver foundand the Version PR job never ran.What
pendingskips a package at0.0.0, with or without a pre-release or build suffix, before any registry or GitHub lookup.publishasks no changelog section of such a package.bump::unreleasedis the one testbump::applyand both call sites share.Queue row VER-077; OpenSpec change
skip-unreleased-package.Proof
a_package_at_0_0_0_plans_nothing:publish --planwith the GitHub API address closed reportsnothing to releaseand writespending=false.publish_asks_no_changelog_of_a_package_at_0_0_0:publishpasses the changelog check and stops at the token check.