chore: add 2.0.4 release verification gate#42
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds a dedicated non-publishing hotfix release verification gate (release:verify) for the 2.0.4 line, wires prepublishOnly to run that full verification gate, and updates publishing documentation to reflect explicit approval expectations.
Changes:
- Add
release:verifyscript (check + E2E + visual + audit + pack dry-run) and makeprepublishOnlyrun it. - Extend package integrity tests to require
release:verifyand assert it remains non-publishing. - Update
docs/PUBLISHING.mdto document the new verification gate and approval requirement language.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| tests/package-integrity.test.js | Adds coverage to ensure release:verify exists, covers the 2.0.4 release gate commands, and remains non-publishing. |
| package.json | Introduces release:verify and updates prepublishOnly to run it. |
| docs/PUBLISHING.md | Documents release:verify as the hotfix verification gate and clarifies the publish flow. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+323
to
+326
| // Keep the hotfix verification gate safe for approval-gated release preparation. | ||
| assert.doesNotMatch(releaseVerify, /\bnpm\s+(?:publish|version)\b/); | ||
| assert.doesNotMatch(releaseVerify, /\bgit\s+tag\b/); | ||
| assert.equal(packageJson.scripts.prepublishOnly, 'npm run release:verify'); |
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.
Summary
release:verifygate to the 2.0.4 hotfix release lineprepublishOnlyto the full hotfix gate instead of onlynpm run checkCurrent branch state
99fdf8d71a23c3bf08b15002b9f91694d702c4femain/ 2.0.4 hotfix release lineui-style-kit-css@2.0.4is not published yetVerification
npm run release:verifynpm run checknpm run test:e2e— 28 passednpm run test:visual— 33 passednpm audit --audit-level=moderate— found 0 vulnerabilitiesnpm run pack:dry-run—ui-style-kit-css-2.0.4.tgz, 30 files, shasumebb90299e3b0720fbcf41abb3c2f9e3a518cf894npm ci --ignore-scripts— 0 vulnerabilitiesnode --test tests/package-integrity.test.jsred/green for the missing release gateNo npm publish, tag, GitHub release, or merge is performed by this PR.