Tag NPM packages from 0.1.x branch as either v1-latest or v1-unstable #193
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
Pushed commits to the main branch published NPM packages tagged as `unstable`, and release tags on the main branch published NPM packaged tagged as `latest`. This conflicted with NPM packages published from the 0.2.x branch and meant that the target Fabric version for the NPM package currently tagged `latest` varied depending on which branch had a release created most recently. The `latest` tag should always correspond to the current Fabric LTS release since it is the default version installed if a specific version is not specified. Also update .gitignore to exclude files that should not be checked in. Signed-off-by: Mark S. Lewis <Mark.S.Lewis@outlook.com>
denyeart
approved these changes
Sep 29, 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.
Pushed commits to the main branch published NPM packages tagged as
unstable, and release tags on the main branch published NPM packaged tagged aslatest. This conflicted with NPM packages published from the 0.2.x branch and meant that the target Fabric version for the NPM package currently taggedlatestvaried depending on which branch had a release created most recently. Thelatesttag should always correspond to the current Fabric LTS release since it is the default version installed if a specific version is not specified.Also update .gitignore to exclude files that should not be checked in.
Contributes to #191