fix(release): allow publishing with no tag; publish one package at a time#1688
Merged
Conversation
v4.x is a maintenance line, so defaulting to 'latest' is wrong (it points npm install at 4.x instead of 5.x). Make dist_tag required with no default and fail fast if it's empty, before the version bump is pushed.
Instead of requiring a tag, when dist_tag is empty run lerna publish without --dist-tag. Modern npm won't move the 'latest' tag when publishing a lower version, so 4.x maintenance releases don't hijack latest.
lucasmcdonald3
changed the title
lucasmcdonald3
changed the title
There was a problem hiding this comment.
Pull request overview
Note
Copilot couldn't run its full agentic review because it didn't start before the timeout. Make sure your repository has a runner available, or add a copilot-code-review.yml file specifying one with the runs-on attribute. See the docs for more details.
Updates the production release workflow to avoid unintentionally moving the latest npm dist-tag when the dist_tag input is empty by omitting --dist-tag entirely.
Changes:
- Clarifies the
dist_tagworkflow input description to indicate empty value publishes without an explicit dist-tag. - Adds conditional logic to run
lerna publishwith--dist-tagonly whenDIST_TAGis non-empty.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
added 4 commits
July 23, 2026 20:24
Serialize package publishes so we don't submit 27 provenance attestations to the Rekor transparency log in parallel, reducing timeout-induced 409s.
…ypes/node subtree)
lucasmcdonald3
changed the title
josecorella
approved these changes
Jul 24, 2026
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.
Issue #, if available:
Description of changes:
dist_tagis empty, do not publish a tag. (Current behavior is to pass an emptydist_tagto the npm CLI, which the CLI interprets as "set latest tag", which we don't want.)--concurrency 1serializes publishes so only one attestation is in flight at a time, (possibly, hopefully) reducing those timeout-induced 409s.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Check any applicable: