managing-prereleases
Skill382 starsChanged 6 days agoISCView on GitHub
Graduate a Changesets 3 prerelease to stable on main, or plan an optional future prerelease cycle on a dedicated branch.
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- audit-convexSkill
- create-changesetSkill
- effectSkill
- release-docsSkill
- upgrade-internal-depsSkill
- upgrade-published-depsSkill
- upgrade-runtime-pinsSkill
- writing-commit-messagesSkill
- writing-technical-documentationSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Keep the final candidate on its prerelease branch until it has passed the required checks.
- Very specific: line 33
Run pnpm changeset pre exit on the graduation branch.
- Very specific: line 38
Do not run stable publishing on the old branch.
- Very specific: line 44
After graduation merges, the existing Changesets action on main runs pnpm version-packages to prepare the stable Version Packages PR.
- Distinctive: line 49
If the user instead asks to include versioning in graduation, run the same command on the graduation branch and review those generated …
- Very specific: line 74
Read the upstream prerelease guide before starting another cycle.
- Distinctive: line 90
Follow the graduation procedure above when the candidate is ready.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Managing prereleases
Stable releases publish from main through .github/workflows/release.yml.
All @confect/* packages belong to one fixed version group. A major can ship
directly from main; a prerelease cycle is optional, not a release requirement.
Graduate a prerelease to stable
Keep the final candidate on its prerelease branch until it has passed the required checks. Prepare graduation separately so removing branch workflows does not disable the final candidate's publication.
- Fetch
mainand the prerelease branch. Reconcile the currentmainhistory with a real merge, not a squash or a content-only replay. Preserve changeset provenance: an ID already in.changeset/pre/must not also be pending in.changeset/. Do not invent a second changeset for changes already shipped under their original ID. - Review
.changeset/pre/and pending changesets for the stable release notes. Changesets 3 moves consumed prerelease changesets into.changeset/pre/; these are inputs to the stable changelog, not disposable artifacts. For an explicitly requested consolidation, account for every consumed and pending entry against the last stable public API and replace them with one reviewed release changeset. Describe final behavior rather than intermediate prerelease migrations, omit changes already released on the stable line, and preserve the existing prerelease changelog sections and Git history. Outside that reviewed consolidation, remove entries only for an explicitly reviewed duplicate or erroneous note. - Run
pnpm changeset pre exiton the graduation branch. This changes.changeset/pre.jsontomode: "exit"; it does not remove the file or change package versions. Never hand-delete that file to exit pre mode. - Set
.changeset/config.jsonbaseBranchtomain, remove the old prerelease branch from workflow triggers, and retire its branch-specific automation. Do not run stable publishing on the old branch. Keepreleaseintact: it is the Mintlify deployment branch, not the package prerelease branch. - Open the graduation PR against
main. Use a merge commit when the PR carries the prerelease history somainretains ancestry. Do not merge without the user's explicit approval. Run the repository checks and backend suites before graduation, and inspect the stable release plan in a disposable checkout. - After graduation merges, the existing Changesets action on
mainrunspnpm version-packagesto prepare the stable Version Packages PR. Thechangeset versionstep consumes the exit state and archived changesets, removespre.jsonand consumed prerelease notes, writes the stable versions, and composes their changelogs. Review that PR before merging it with approval. If the user instead asks to include versioning in graduation, run the same command on the graduation branch and review those generated changes there; do not version both ways. - On the merged stable version commit,
release.ymlrunspnpm release(pnpm build && changeset publish). Verify the npm versions andlatestdist-tags, release tags, and docs deployment before reporting completion. Retire the old package prerelease branch only after explicit approval; never deletereleaseas part of that cleanup.
The exit behavior above was checked with Changesets 3.0.3 in an isolated
workspace: 1.0.0 plus a major changeset became 2.0.0-next.0, then pre exit
left mode: "exit", and the following version produced 2.0.0, removed the
pre state, and included the archived note in the stable changelog. Recheck this
behavior when upgrading Changesets; do not simulate graduation in the active
checkout unless versioning is actually requested.
Documentation releases
Mintlify serves one current site from release:apps/docs. A successful stable
package publish deploys the matching main commit. Docs-only deployments use
the release-docs skill. Old versioned page URLs redirect to the current pages;
there is no archived site or version selector.
Optional future prereleases
Read the upstream prerelease guide
before starting another cycle. Use a dedicated vN branch, never main, so
stable fixes can continue publishing independently.
- Set that branch's Changesets
baseBranchtovNand runpnpm changeset pre enter next. Add a changeset for the intended major bump. - Extend the existing
release.ymland ordinary CI triggers forvNin a reviewed change. Reuserelease.yml: npm trusted publishing is tied to its filename. Keep docs deployment restricted tomain; prereleases must not replace the public stable docs. Use a separate preview if one is needed. - Version and publish iterative candidates through Changesets, retaining the
.changeset/pre/provenance. Verify npm dist-tags, especially when introducing a package that has never been published. Consumers opt in with@next. - Merge current
mainintovNat each checkpoint and inspect changeset IDs, retractions, and dependency conflicts explicitly. There are no active sync jobs or freshness-label checks; add automation only when a new cycle needs it. - Follow the graduation procedure above when the candidate is ready.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

