Promote Plate beta releases, sync main back to next and verify published npm/GitHub state with release authority.
80%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.agents/skills/release-lanes/SKILL.mdUse this when the user asks to maintain Plate latest and beta, promote beta
to stable, sync main into next, recover release lane drift, verify npm
dist-tags, or run the release lane after a stable release.
CI owns publishing. This skill owns lane maintenance.
Do not create a routine main -> next sync PR. That path creates review churn
for deterministic release metadata conflicts. Sync directly with a merge commit,
repair known release metadata automatically, push next, then let release.yml
publish beta.
main publishes stable packages with npm tag latest.next publishes prerelease packages with npm tag beta. While the repository variable SKIP_NEXT_CI is true, release.yml skips on next, so nothing publishes until someone deletes the variable..changeset/pre.json belongs on next only.main must never publish while .changeset/pre.json exists.Package publication runs pnpm plite:release:packages and does not imply broad
Plite behavior readiness. No CI workflow runs the Plite browser lanes, so a
release-ready claim needs each lane run locally from a clean checkout at the
exact release commit, the browser matrix (pnpm check:plite:browser-matrix)
included, with each lane's log cited. Make that claim only when the user
explicitly asks for it. Do not infer broad readiness from source tests,
historical artifacts, or package proof.
These are skill arguments, not subcommands of release-branch-prs.mjs.
| Invocation | Action |
|---|---|
release-lanes status | Read branch, workflow and npm state. |
release-lanes sync | Dry-run, then perform and push the direct main-to-next sync. |
release-lanes sync dry-run | Inspect the direct sync without committing or pushing. |
release-lanes promote or promote dry-run | Dispatch the promotion workflow with dry_run=true. |
release-lanes promote execute | Dispatch with dry_run=false; verify the generated next-to-main PR. Merge only with merge authority. |
release-lanes verify | Read release workflows, npm tags and GitHub releases. |
release-lanes full <scope> | Status, the explicitly requested promotion/merge or sync steps, then verification. No unrelated release operation is implied. |
Read state only:
git fetch origin main next
gh pr list --base main --head next --state open --json number,title,url,state
gh run list --workflow release.yml --branch main --limit 5 \
--json databaseId,status,conclusion,createdAt,url
gh run list --workflow release.yml --branch next --limit 5 \
--json databaseId,status,conclusion,createdAt,url
npm view platejs dist-tags --jsonRecord:
origin/main SHAorigin/next SHAorigin/next:.changeset/pre.json exists and has tag betaplatejs dist-tags for latest and betasync/main-to-next PRs, if anyThis fast mode is the whole direct sync recipe. It skips planning and panel review unless a planning artifact was requested.
Run after a stable release, after merging a promote PR, or whenever main has
commits missing from next.
Dry run first:
node tooling/scripts/release-branch-prs.mjs sync-main-to-next --dry-runThen run the direct sync from a clean detached worktree, never from the shared checkout. The real sync checks out origin/next detached in whatever checkout runs it, and it refuses local changes. Create the worktree with git worktree add --detach ../plate-sync origin/next, run pnpm install there, and run the sync from it. Remove it afterward with git worktree remove ../plate-sync.
For an explicit dry-run request, stop after the dry run and report it.
node tooling/scripts/release-branch-prs.mjs sync-main-to-next --pushThe script must:
main and nextorigin/next, leaving local branches and the git identity unchangednext beta package versions over main stable versions.changeset/pre.json from next, or create beta pre mode in the same
sync commit when next is out of pre mode after promotionmainmain
commits so the beta lane can publish those fixespnpm ci:version before committing when beta changesets are generated,
so next receives versioned beta package metadata instead of a pending
Version Packages PR[skip release] sync commit only when no beta changesets were generatedverify-main-to-next-syncorigin/next; a push you type yourself starts with
PSTACK_RELEASE=1, because guard.mjs denies every other agent push to
next outside land.mjsIf the script stops on files outside known release metadata, do not guess. Resolve only when source ownership is obvious; otherwise stop with exact files.
Then watch only the workflows created by the pushed sync commit:
gh run list --branch next --limit 10 \
--json databaseId,name,workflowName,headSha,status,conclusion,displayTitle,url
gh run watch <release-run-id> --exit-status
gh run watch <ci-run-id> --exit-statusAfter a beta-to-stable promotion, next may be out of prerelease mode. The
direct main -> next sync restores beta pre mode in the same unskipped merge
commit, so the next release workflow can publish the generated beta changesets.
Use a standalone beta re-entry commit only when no direct sync is needed and no beta changesets need publication:
git switch next
git pull --ff-only origin next
pnpm changeset pre enter beta
git add .changeset/pre.json
git commit -m "chore: enter beta pre-release mode [skip release]"
PSTACK_RELEASE=1 git push origin nextIf .changeset/pre.json already exists with { "mode": "pre", "tag": "beta" },
record N/A and do not create a duplicate commit.
Run dry first unless the user explicitly asks for the real promotion:
gh workflow run promote.yml --ref next -f dry_run=true
gh run watch <run-id> --exit-statusFor a real promotion:
gh workflow run promote.yml --ref next -f dry_run=false
gh run watch <run-id> --exit-statusThen review the generated next -> main PR:
mainnext.changeset/pre.json-beta.*Merge the promote PR only when the user explicitly authorized that merge as part of the release request. Use a merge commit, not squash or rebase.
Watch release workflows:
gh run list --workflow release.yml --branch main --limit 5 \
--json databaseId,status,conclusion,createdAt,url
gh run list --workflow release.yml --branch next --limit 5 \
--json databaseId,status,conclusion,createdAt,urlVerify npm:
npm view platejs dist-tags --json
npm view platejs@latest version
npm view platejs@beta versionVerify GitHub releases:
gh release list --limit 10Close stale sync/main-to-next PRs after direct sync succeeds:
gh pr list --base next --head sync/main-to-next --state open --json number,url
gh pr close <number> --comment "Closing because release-lanes synced main directly into next."Do this only after direct sync and verification pass and the active request authorizes closing the stale PRs and posting the cleanup message.
Stop only for:
.changeset/pre.jsonlatest or beta points at an unexpected version after publicationudecode/plate
e94b0d1
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.