feat(semrel): npm publish through the monorepo release train #59

Merged
ryangr0 merged 1 commit from feat/monorepo-npm-publish into main 2026-09-04 04:51:32 +00:00
Owner

Adds an optional NPM_TOKEN secret to semantic-release-monorepo.yml, passed through to the composite as the env @semantic-release/npm reads. The plugin writes its own .npmrc from the package's publishConfig.registry + token, so the train still installs nothing (ADR-0005) and needs no npm config commands. Empty is inert for tag/changelog-only trains.

This retires the reason npm-publishing repos had to carry a self-contained release.yml: webgrip/frontend-toolkit switches to four thin callers into this lane on this PR's tag, which also gives it the lane's seeded <name>-v0.0.0 baseline — first feat releases 0.1.0, per the org's start-from-0.0.0 rule. (semantic-release-config itself must stay self-contained: the lane's toolchain image bakes the package it releases.)

After merge: note the tag; frontend-toolkit PR #1's release.yml gets pinned to it before that PR merges.

🤖 Generated with Claude Code

Adds an optional `NPM_TOKEN` secret to `semantic-release-monorepo.yml`, passed through to the composite as the env `@semantic-release/npm` reads. The plugin writes its own .npmrc from the package's `publishConfig.registry` + token, so the train still installs nothing (ADR-0005) and needs no npm config commands. Empty is inert for tag/changelog-only trains. This retires the reason npm-publishing repos had to carry a self-contained release.yml: `webgrip/frontend-toolkit` switches to four thin callers into this lane on this PR's tag, which also gives it the lane's seeded `<name>-v0.0.0` baseline — first `feat` releases **0.1.0**, per the org's start-from-0.0.0 rule. (`semantic-release-config` itself must stay self-contained: the lane's toolchain image bakes the package it releases.) **After merge:** note the tag; frontend-toolkit PR #1's release.yml gets pinned to it before that PR merges. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
feat(semrel): npm publish through the monorepo release train
Some checks failed
docker-build-and-push-registry.yml / Merge pull request 'feat(semrel): npm publish through the monorepo release train' (#59) from feat/monorepo-npm-publish into main (pull_request) Failing after 0s
docker-build-and-push.yml / Merge pull request 'feat(semrel): npm publish through the monorepo release train' (#59) from feat/monorepo-npm-publish into main (pull_request) Failing after 0s
forgejo-distribute.yml / Merge pull request 'feat(semrel): npm publish through the monorepo release train' (#59) from feat/monorepo-npm-publish into main (pull_request) Failing after 0s
github-distribute.yml / Merge pull request 'feat(semrel): npm publish through the monorepo release train' (#59) from feat/monorepo-npm-publish into main (pull_request) Failing after 0s
github-issue-create-by-prompt.yml / Merge pull request 'feat(semrel): npm publish through the monorepo release train' (#59) from feat/monorepo-npm-publish into main (pull_request) Failing after 0s
github-issues-create-by-prompt.yml / Merge pull request 'feat(semrel): npm publish through the monorepo release train' (#59) from feat/monorepo-npm-publish into main (pull_request) Failing after 0s
helm-chart-deploy.yml / Merge pull request 'feat(semrel): npm publish through the monorepo release train' (#59) from feat/monorepo-npm-publish into main (pull_request) Failing after 0s
helm-chart-push.yml / Merge pull request 'feat(semrel): npm publish through the monorepo release train' (#59) from feat/monorepo-npm-publish into main (pull_request) Failing after 0s
helm-charts-deploy.yml / Merge pull request 'feat(semrel): npm publish through the monorepo release train' (#59) from feat/monorepo-npm-publish into main (pull_request) Failing after 0s
helm-charts-push.yml / Merge pull request 'feat(semrel): npm publish through the monorepo release train' (#59) from feat/monorepo-npm-publish into main (pull_request) Failing after 0s
laravel-quality.yml / Merge pull request 'feat(semrel): npm publish through the monorepo release train' (#59) from feat/monorepo-npm-publish into main (pull_request) Failing after 0s
php-application-static-analysis.yml / Merge pull request 'feat(semrel): npm publish through the monorepo release train' (#59) from feat/monorepo-npm-publish into main (pull_request) Failing after 0s
rust-semantic-release.yml / Merge pull request 'feat(semrel): npm publish through the monorepo release train' (#59) from feat/monorepo-npm-publish into main (pull_request) Failing after 0s
semantic-release-monorepo.yml / Merge pull request 'feat(semrel): npm publish through the monorepo release train' (#59) from feat/monorepo-npm-publish into main (pull_request) Failing after 0s
semantic-release.yml / Merge pull request 'feat(semrel): npm publish through the monorepo release train' (#59) from feat/monorepo-npm-publish into main (pull_request) Failing after 0s
setup-repository-bootstrap.yml / Merge pull request 'feat(semrel): npm publish through the monorepo release train' (#59) from feat/monorepo-npm-publish into main (pull_request) Failing after 0s
setup-repository-copilot-files.yml / Merge pull request 'feat(semrel): npm publish through the monorepo release train' (#59) from feat/monorepo-npm-publish into main (pull_request) Failing after 0s
setup-repository-create-from-template.yml / Merge pull request 'feat(semrel): npm publish through the monorepo release train' (#59) from feat/monorepo-npm-publish into main (pull_request) Failing after 0s
spa-preview.yml / Merge pull request 'feat(semrel): npm publish through the monorepo release train' (#59) from feat/monorepo-npm-publish into main (pull_request) Failing after 0s
static-analysis.yml / Merge pull request 'feat(semrel): npm publish through the monorepo release train' (#59) from feat/monorepo-npm-publish into main (pull_request) Failing after 0s
sync-template-files.yml / Merge pull request 'feat(semrel): npm publish through the monorepo release train' (#59) from feat/monorepo-npm-publish into main (pull_request) Failing after 0s
techdocs-deploy-backstage-s3.yml / Merge pull request 'feat(semrel): npm publish through the monorepo release train' (#59) from feat/monorepo-npm-publish into main (pull_request) Failing after 0s
techdocs-deploy-codeberg.yml / Merge pull request 'feat(semrel): npm publish through the monorepo release train' (#59) from feat/monorepo-npm-publish into main (pull_request) Failing after 0s
techdocs-deploy-docs-site.yml / Merge pull request 'feat(semrel): npm publish through the monorepo release train' (#59) from feat/monorepo-npm-publish into main (pull_request) Failing after 0s
techdocs-deploy-gh-pages.yml / Merge pull request 'feat(semrel): npm publish through the monorepo release train' (#59) from feat/monorepo-npm-publish into main (pull_request) Failing after 0s
tests.yml / Merge pull request 'feat(semrel): npm publish through the monorepo release train' (#59) from feat/monorepo-npm-publish into main (pull_request) Failing after 0s
update_mkdocs.yml / Merge pull request 'feat(semrel): npm publish through the monorepo release train' (#59) from feat/monorepo-npm-publish into main (pull_request) Failing after 0s
update_techdocs.yml / Merge pull request 'feat(semrel): npm publish through the monorepo release train' (#59) from feat/monorepo-npm-publish into main (pull_request) Failing after 0s
wordpress-plugin-release-distribute.yml / Merge pull request 'feat(semrel): npm publish through the monorepo release train' (#59) from feat/monorepo-npm-publish into main (pull_request) Failing after 0s
wordpress-plugin-release.yml / Merge pull request 'feat(semrel): npm publish through the monorepo release train' (#59) from feat/monorepo-npm-publish into main (pull_request) Failing after 0s
bb2bbbf463
Optional NPM_TOKEN secret on semantic-release-monorepo.yml, passed through
to the composite as the env @semantic-release/npm reads. The plugin writes
its own .npmrc from the package's publishConfig.registry plus the token, so
the train needs no npm config commands and installs nothing, per ADR 0005.
Empty stays inert for tag/changelog-only configs. This retires the reason
npm-publishing repos (semantic-release-config, now frontend-toolkit) had to
carry a self-contained release pipeline instead of this lane.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign in to join this conversation.
No reviewers
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
webgrip/workflows!59
No description provided.