[Backport v1.x] Add support for publishing legacy versions in release script #233
Conversation
This file contains 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
## Summary Releasing earlier versions to npm is a pain. This PR ensures we: 1. Find the actual latest version of the package 2. Publish the legacy version using the `latest` tag, ensuring semver updates work as expected 3. Re-tag `latest` as the version found in step 1 Following this, we should be ready to support backporting and legacy releases purely with labels and PRs. 🥳 ## Related - mermaid-js/mermaid#4200 - bower/bower#2041 - npm/npm#6778 (cherry picked from commit 55c3b1c)
|
jpwilliams
approved these changes
Jun 12, 2023
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.
Backport 55c3b1c from #230.