docs(skill): fold v0.3.0 release learnings into the release-manager skill - #2548
Open
fengmk2 wants to merge 1 commit into
Open
docs(skill): fold v0.3.0 release learnings into the release-manager skill#2548fengmk2 wants to merge 1 commit into
fengmk2 wants to merge 1 commit into
Conversation
…kill Adds a registry-visibility gate after npm publish. A green Release job only means the registry accepted the request; v0.3.0 shipped with vite-plus on latest depending on a core version that stayed invisible for about 35 minutes, breaking every install and failing the Docker and docs jobs. Also drops the PR-title opener from the body template, records that Docs covers the published site rather than contributor files, keeps resolution logic out of entries, requires a migration path on breaking changes, and stops posting the Discord draft to the release PR.
✅ Deploy Preview for viteplus-preview canceled.
|
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.
Folds the durable learnings from the v0.3.0 release into the release-manager skill.
Registry visibility after npm publish.
pnpm publishprints✅ Published package <name>@X.Y.Zwhen the registry accepts the request, not when it serves the version. In v0.3.0 theReleasejob went green, but@voidzero-dev/vite-plus-core@0.3.0stayed invisible for about 35 minutes whilevite-plus@0.3.0was already on thelatesttag depending on it. Every install failed withETARGET, and the Docker and docs jobs failed too. Step 7 now adds a cache-busting visibility check between publish and the downstream jobs, with the rollback command and a real temp-dir install to confirm.Changelog rules. Docs covers the published docs site, so a
docscommit touching an RFC,AGENTS.md, or a skill goes in Chore. Entries describe behaviour, not resolution logic. A breaking change states its migration path.Smaller corrections. Drop the
Release vite-plus vX.Y.Z: ...opener from the body template, since it duplicated the PR title and step 8 stripped it again. Hand the Discord draft over in chat instead of commenting it on the release PR.