docs(skill): report publish backlog in the release skill#229
Merged
Conversation
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
1 participant
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.
Follow-up to #228. The
releaseskill's reporting step now makes the "bumped but not yet on npm" state explicit.Step 5 (renamed Report the release set + the publish backlog) now tells the runner to report two distinct things:
name: old → new.mainversion is ahead of npm latest (npm view <pkg> version), i.e. what actually awaits the external private-mirror publish — including packages bumped earlier that the mirror hasn't published yet (e.g.ai-sdk-providermain 0.4.0 vs npm 0.1.1).It also reminds the runner not to call a package "released" at this stage — this repo only produces the version bump; nothing here pushes to npm.