chore(skills): add release-manager skill for the standard release process#2019
Draft
fengmk2 wants to merge 15 commits into
Draft
chore(skills): add release-manager skill for the standard release process#2019fengmk2 wants to merge 15 commits into
fengmk2 wants to merge 15 commits into
Conversation
…cess Documents the vite-plus release process end-to-end so any maintainer can act as release manager: prepare_release workflow, the required binding/index.cjs version sync, changelog PR description rules and validation, pkg.pr.new smoke builds, release-branch CI failure protocol (fix via separate PR to main, merge back, update changelog), the release.yml pipeline including the manual environment approval, and post-release verification and announcement steps.
✅ Deploy Preview for viteplus-preview canceled.
|
Add a Usage section: no-arg and version-arg forms start a new release, while a release PR URL/number means taking over an in-flight release, auditing which steps are already done before continuing.
… test The smoke test is optional, so the agent must ask the release manager whether to run it instead of adding the label or skipping on its own. When accepted, verify the published build against a real project with the test-pkg-pr-new-migrate skill and report the outcome. Add the matching checklist item.
Swap steps 3 and 4: write the release PR description first, then offer the optional pkg.pr.new smoke test, which always runs before merging. Update the pipeline overview, take-over audit order, and step cross-references to match.
Documents the v0.2.2 (PR #2016) smoke test run: choosing a target project pinned to the previous release for a real upgrade path, passing the full build commit SHA when the PR head has moved, the shape of a passing run, and the single-version pass criteria with the release-blocker rule on failure.
The harness resolves a PR number through the bridge x-commit-key header to the latest published immutable commit and prints the resolved SHA, so the PR number is the right default; a full commit SHA is only needed to pin a specific build when several have been published.
…pull Post-release Docker verification now runs vp --version in the image and checks the reported version and bundled tool versions against the changelog's Bundled Versions table. Update the checklist to match.
Highlights are one short line each instead of heading-plus-explanation sentences, the secondary list is 4-6 short bullets, and the whole message targets about 20 lines.
- Take-over audit covers the already-merged state (Release workflow run, generated release-body stub) continuing at step 7 or 8. - Blog-post coordination: read the preview, align the theme, link the final URL even before it is live. - Release notes polish is ask-first: present the draft to the release manager before gh release edit; document the exact PR-body transformation, the release retitle, the Docker usage block at the end of Installation, and post-apply validation. - Verification: add the dist-tags check, note that Already up to date passes, and add the GHCR token+manifest fallback when no local Docker daemon is running. - Discord: never post directly; share the draft as a fenced code block comment on the release PR so mentions do not ping and emoji stay literal.
- Step 2: add an explicit after-check that both stale-version grep counts are zero after the binding/index.cjs replacement. - Step 5: do not assume a main merge only brings the fix PR; list the full incoming range and add a changelog entry for every newly included PR. - Step 7/8: the Release job also publishes the platform-native @voidzero-dev/vite-plus-cli-<platform> packages via publish-native-addons.ts; spot-check one of them during npm verification.
Document the ecosystem-ci org as the catalog of smoke-test projects: pick one whose stack matches the release's risk area and whose pinned vite-plus is older than the release so migrate does a real upgrade; clone it locally for the test-pkg-pr-new-migrate harness. Correct the v0.2.2 example wording (the forks are not uniformly on the previous release; vibe-dashboard happened to be on 0.2.1).
Clone ecosystem-ci projects under ~/git/github.com/vite-plus-ecosystem-ci/<repo> so all smoke-test checkouts live in one directory and the test environment can be removed in a single rm -rf after the release. Update the example path to match.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
… test PRs target the fork Slim step 4's target/setup prose to link the canonical guidance in vite-plus-ecosystem-ci/.github (TESTING.md + ecosystem.json), add a bold mandatory rule that test PRs must target the fork (gh pr create defaults to the upstream parent), and fix the clone snippet to check out the fork's tracked branch.
This comment was marked as resolved.
This comment was marked as resolved.
…preview build Preview builds now publish/install through the registry bridge (PR #2038), not pkg.pr.new. Rename step 4 to "preview build smoke test", switch the trigger label to preview-build, use the "Publish preview build" workflow name, and drop the pkg-pr-new bot / install-URL references. Kept names that #2038 preserves: the publish-to-pkg.pr.new.yml filename and the test-pkg-pr-new-migrate script/skill.
Add a concise pointer to TESTING.md's 'Smoke-test via a fork PR' (branch update-vite-plus-prerelease-test-<version> from source, draft PR on the fork assigned to the release manager, watch CI), plus the non-standard-installer caveat (cnpmcore's utoo). Detail stays in TESTING.md.
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.
For human usage: