Repository navigation
[WTF-2832]: Apply latest dist tag - #245
Merged
Merged
Conversation
alihcsumer
reviewed
Nov 3, 2026
weirdwater
force-pushed
the
wtf/2832-dist-tags
branch
from
November 3, 2026 14:08
30d9940 to
6e93926
Compare
alihcsumer
approved these changes
Nov 3, 2026
This branch was successfully deployed
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.
Since we introduced backports, the publish to npm script has stopped applying the
latesttag.This PR moves the logic into a node script for clarity
Testing
A commit was added allowing the pipeline to test against a test package. This needs to be removed before merge.
At time of test, the latest version of the
testpackage on npm was3.3.0Publishing a latest version
test-v3.4.0latestPublishing a backport version
test-v3.2.53.2-latestTo Do