ci: make npm publish dist-tag an explicit choice (0.9) - #1350
Merged
Conversation
Backport of #1348 to release/0.9, so this line is ready to publish under `legacy` (or a line-scoped `v0.9`) once 0.10 takes over `latest`. The `latest-build` boolean mapped anything other than true to nightly - both the `executorch-nightly` dist-tag and a rewritten version - which is how 0.8.5 went out as 0.8.5-nightly-6e1cb0a-20260803. Needed on this branch because workflow_dispatch reads the workflow definition from the selected ref.
12 tasks
barhanc
approved these changes
Aug 4, 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
2 participants
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.
Description
Previously publish without
latestchecked published as nightly. But sometimes we want to publish new legacy version. This PR adds this possibility.Introduces a breaking change?
Type of change
Tested on
Testing instructions
Actions → NPM publish → Run workflow → ref
release/0.9. The form now shows arelease-typedropdown withnightly/latest/legacyinstead of a checkbox.Screenshots
Related issues
Checklist
Additional notes
Backport of #1348, staged so 0.9 is ready when 0.10 takes over
latest.