Improve diffbudget release documentation#5
Open
rogerchappel wants to merge 2 commits into
Open
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.
What changed
SECURITY.mdto the npm package allowlist so the published tarball carries vulnerability reporting guidance.dbudgetalias in the quickstart.npm run package:smokeandnpm run release:checkto README verification commands.Why it matters
Users can discover both shipped CLI names and run the same release gates maintainers use before changing CLI behavior or publishing. The package dry run now confirms the security policy ships with the package.
Verification
npm ci-> passed, 0 vulnerabilitiesnpm run release:check-> passed; 10 tests passed, smoke ok, npm pack dry-run includedSECURITY.mdnode /Users/roger/Developer/my-opensource/releasebox/bin/releasebox.js check .-> passedRemaining limitations / follow-up