Repository navigation
ci(release): call the shared npm release workflow - #9
Merged
Merged
Conversation
publish-npm.yml now calls PerfectPan/gh-repo-checks' npm-release.yml with the default inputs, and CI runs its release-plan check. The local release-plan and first-publish scripts, their tests and their helper dependencies are gone, and the runbook keeps only what the template decides, linking the shared runbook for the rest. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
Summary
The template's Release workflow becomes a caller of the shared workflow
PerfectPan/gh-repo-checks/.github/workflows/npm-release.yml@v1(gh-repo-checks v1.3.0). Repositories created from the template then start on the shared release flow instead of copies of it.publish-npm.ymlkeeps its file name for trusted publishers and calls the shared workflow with the default inputs:pnpm run check,pnpm audit --prod --audit-level=high,pnpm run version-packagesand the first-publish check.scripts/check-release-plan.mjsandscripts/check-first-publish.mjs;@changesets/config,@changesets/get-release-plan,@changesets/should-skip-packageand@manypkg/get-packages.ci.ymlrunsgh repo-checks release-planafter the install, andpnpm run checkno longer runs the local copy. Thescriptspackage keeps itstestscript with--passWithNoTests.docs/development/release.mdkeeps what the template decides: changeset rules, versioning, first release and the example package's setup, bot PRs and CI policy. For the jobs, release steps and recovery it links the shared runbook. README follows.The example package is private, so Release runs in mode
noneon every push here. Its first run is a no-risk check that the shared select job checks out gh-repo-checks atjob.workflow_sha.Validation
pnpm install, thenpnpm install --frozen-lockfile: ok. The lockfile only drops the four helper packages.pnpm run check: passed.gh repo-checks release-planreports ok with 0 records.gh repo-checks first-publish versionreports ok.actionlint1.7.12 on.github/workflows/*.yml: passed.gh repo-checks repository --staged: ok.reviewersubagent reviewed this branch.none.