[fengmk2]

Fold the durable lessons from the v1.5.0 and v1.5.1 releases into the release-manager skill.

From v1.5.0

• Homebrew (step 2): before merging, run test-homebrew.yml by hand on the release branch to install the release head through a disposable tap on macOS ARM64 and Linux. A sandboxed agent cannot run brew install, because Homebrew refuses an inherited sandbox that can write to its prefix.
• Changelog credits (step 3): check commit authors for every changelog PR, not only bot or carried-over PRs, and credit maintainers whose commits change code. Test-, snapshot-, and doc-only touch-ups do not earn credit.
• Changelog style (step 3): do not name a few upgraded tools in the opening sentence when several moved. Put commands in a code block under the list item, without a blank line before the fence, because that blank line makes the whole list loose on GitHub.
• Fork smoke PRs (step 4): keep descriptions, comments, and commit messages free of references to vite-plus PRs or issues. GitHub keeps each cross-reference on the vite-plus timeline even after the text is edited.
• Preview rebuilds (step 4): relabeling to rebuild the preview also restarts the PR's CI, and the cancelled run shows a failed done check until the new run finishes.
• Triage (step 4): add stale pnpm metadata cached under the bridge registry, forks whose Actions GitHub disabled without the setting showing it, and AGENTS.md checks that see the preview docs origin.
• Carried-over fixes (step 4): drop fixes that upstream made obsolete, redo restored dependency pins with the bundled versions, and reinstall after re-applying package.json changes so the lockfile matches.
• Release notes (step 8): add a Homebrew block to the Installation section once the release's formula PR is merged.
• Upgrade check (step 8): replace an awk snippet whose positional fields the skill loader replaced with the invocation arguments, and record in step 9 that the skill must not contain positional references.

From v1.5.1

• Security entries (step 3): a security fix in vite-plus's own code goes first in Fixes & Enhancements with a Security: label, not in Features. Security fixes from upstream dependency upgrades still lead Features.
• Draft advisories (step 3): match the repository's draft advisories to their fix PRs. Until an advisory is published, describe the fix by its behavior only, and keep the reporter's co-author credit. After publication, add the severity and the advisory link to the release notes and the announcement, and link the repository advisory page until the global advisory database lists it.
• Cancelled checks (step 5): each label added to the release PR starts a new set of runs and cancels the set in progress. A cancelled matrix job can show as a failed check with an unexpanded name, so confirm a later run of the same workflow passed on the same head.
• Native-addon publish (step 7): the native-addon step can time out while npm processes one platform package. No vite-plus or core version is published before that step passes. Wait until npm serves the package, then use "Re-run failed jobs" and confirm the skip line for each platform package.
• Release notes validation (step 8): after the merge, generate-notes also lists the release PR itself, which is not a changelog entry.
• Local Homebrew check (step 8): keep the isolated prefix out of Homebrew's temporary directory. When the agent sandbox or a TLS-inspecting proxy blocks the local check, report the Published Homebrew CI checks as the evidence and give the release manager the local command.
• X replies (step 8): read contributors' X handles from their GitHub profiles, and use the GitHub profile URL when no X account is listed.

🤖 Generated with Claude Code

[cloudflare-workers-and-pages]

🚀 Deploying Preview to Cloudflare 🚀

Preview URL: https://docs-release-manager-v1-5-0-learnings-viteplus-dev.voidzero-docs.workers.dev (commit dce4307)

This URL reflects your latest Preview deployment

Preview Deployments by commit

Status	Deployment URL	Commit	Updated (UTC)	See this deployment's details
Build: Success ✅ Deployment: Success ✅ View logs ↗	https://42411251-viteplus-dev.voidzero-docs.workers.dev	dce4307	2026-11-10T03:11:36.197Z	Visit the dashboard ↗
Build: Success ✅ Deployment: Success ✅ View logs ↗	https://dc7ca43d-viteplus-dev.voidzero-docs.workers.dev	5614cb6	2026-11-04T05:44:29.441Z	Visit the dashboard ↗