Always set latest tag in publish code#1255
Merged
jakebailey merged 2 commits intomainfrom Feb 17, 2026
Merged
Conversation
andrewbranch
approved these changes
Feb 17, 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.
An explicit
undefinedhere actually caused the tag to be removed from the publisher options via object spread, so we were managing to publish deprecated versions repeatedlywithout a tagwith a tag namedundefined.I wasn't even aware that it was possible to publish a package without a tag (we have code that explicitly works around this fact!), so maybe that code could go away with this new knowledge.But for now, restore the old publisher behavior where we'd publish with
latestby default.I've run the publisher from this branch and it works.
Fixes #1254