Skip to content

Update release preparation guidelines #1913

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Dirk Bäumer (dbaeumer) merged 1 commit into from
Oct 22, 2026
Merged

Update release preparation guidelines #1913

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 10 additions & 7 deletions .github/skills/prepare-release/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,7 @@ allow corrections. Explain any unresolved policy choices before asking.
**Wait for explicit approval before editing manifests or mutating GitHub.**
If the user revises the proposal, use the approved numbers, not the original ones.

## 3. Update manifests consistently
## 3. Update manifests and release history

- Update approved versions in package `package.json` files.
- Find every reference to affected local npm packages in all manifests, including
Expand All @@ -70,8 +70,10 @@ If the user revises the proposal, use the approved numbers, not the original one
Otherwise report that lockfiles were not regenerated.
- Do not use `npm version`, `update:lock`, `all:publish`, `npm pack`, or publishing
commands as shortcuts: lifecycle hooks can clean files or run release actions.
- If requested, update the root README release history in its existing style,
including compatibility notes and milestone query links.
- Update the root `README.md` release history as part of release preparation;
do not wait for a separate request. Follow its existing style, use the approved
package versions, and include compatibility notes, relevant fixes and
improvements, and fixed-issue and merged-PR query links for the protocol milestone.

## 4. Validate before updating GitHub

Expand Down Expand Up @@ -117,7 +119,8 @@ restrictions or claim success. Stop before milestone mutations until resolved.

## Completion report

Report the approved versions, manifest changes, actual validation result, and
milestone link with counts of assigned PRs and fixed issues. Mention exclusions,
preserved milestones, lockfile status, and any blockers. Do not describe packages
as published or tests as passed when those actions were not performed.
Report the approved versions, manifest and README release-history changes, actual
validation result, and milestone link with counts of assigned PRs and fixed issues.
Mention exclusions, preserved milestones, lockfile status, and any blockers. Do
not describe packages as published or tests as passed when those actions were not
performed.
Loading