Cut a fresh publishable Guardex release after npm lagged#390
Merged
Conversation
The last GitHub release reached v7.0.25, but the npm registry still reported @imdeadpool/guardex@7.0.24. This bumps the package to 7.0.26, records the matching README release note, and keeps the lane release-only so the next GitHub release can drive a clean publish retry from current main. Constraint: npm cannot republish an existing version once GitHub release metadata is already ahead of the registry Rejected: Reuse 7.0.25 | npm registry still shows 7.0.24, so a fresh semver is required for another publish attempt Confidence: high Scope-risk: narrow Directive: Keep release-only lanes limited to semver plus README release notes unless the publish failure points back to package metadata or workflow code Tested: node --check bin/multiagent-safety.js; openspec validate --specs; node --test test/metadata.test.js; node --test test/release.test.js; npm pack --dry-run Not-tested: full npm test clean exit; this run hung after passing printed subtests because test/sandbox.test.js left a child codexAgent process alive
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
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.
Automated by gx branch finish (PR flow).