Release GraphKeeper 0.1.3 - #4
Merged
Merged
Conversation
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.
Outcome
Prepare the verified
graphkeeper@0.1.3release candidate. This PR does not publish to npm, create a tag, or create a GitHub release.Release contents
0.1.3CHANGELOG.mdand include it in the npm packagenpm publish --dry-run0.1.3Verification
npm cinpm run release:verify: 247 functional/unit/integration/e2e/security tests and 2 isolated packaging tests passednpm run test:security: 14 passednpm run test:performance: 5 passed; peak memory 57.35 MBnpm ls --all: valid dependency tree--version,init,check,query, anddoctorpassednpm publish --dry-run --access public: passed; nothing publishedFinal candidate tarball:
graphkeeper-0.1.3.tgz9dcb264e9143a75f9e817bd62836dea82cbf39cesha512-tJ2vtvovS83CKj/vFJqQmGG/L/rTpzpHOZhaS3Apej7b4hh3TvHWPgdiKwIbdqv6Yx0W/0gZ0Eyxsym315Hpog==Publication boundary
The public package owner is
anusbutt, but this environment currently returnsE401fornpm whoami. After this PR is merged, authenticate npm explicitly and obtain a separate publish decision before publishing. Tagging and GitHub release creation must happen only after the registry package is verified.