feat(semrel): npm publish through the monorepo release train #59
No reviewers
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
webgrip/workflows!59
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/monorepo-npm-publish"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Adds an optional
NPM_TOKENsecret tosemantic-release-monorepo.yml, passed through to the composite as the env@semantic-release/npmreads. The plugin writes its own .npmrc from the package'spublishConfig.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-toolkitswitches to four thin callers into this lane on this PR's tag, which also gives it the lane's seeded<name>-v0.0.0baseline — firstfeatreleases 0.1.0, per the org's start-from-0.0.0 rule. (semantic-release-configitself 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