Uh oh!
There was an error while loading. Please reload this page.
docs: update release process for git-dependency consumption - #7
Closed
vivek-perforce wants to merge 1 commit into
Closed
docs: update release process for git-dependency consumption#7vivek-perforce wants to merge 1 commit into
vivek-perforce wants to merge 1 commit into
Conversation
The Nexus registry this package used to publish to has been retired. Consumers now install it via a git URL, and prepare builds lib/ automatically, so npm publish is no longer part of the release flow.
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Documents the actual release process now that this package is installed as a git dependency (see #5, #6) rather than published to Nexus:
npm run patch-release/etc. steps (which end innpm publish) withnpm version patch/minor/major+ push tag.preparebuildslib/automatically for git-dependency installs, so publishing isn't needed.release/patch-release/etc. scripts in package.json as legacy, tied to the retired Nexus registry.Test plan
Docs-only change, no code affected.