Merged
Conversation
The npm registry already serves 7.0.19, so this advances the package metadata and README release history to 7.0.20 for the next publishable cut. Constraint: npm will not republish an existing semver Rejected: Reuse 7.0.19 | npm already serves that version Confidence: high Scope-risk: narrow Reversibility: clean Directive: Keep README release notes aligned with every future package version bump Tested: npm test; node --check bin/multiagent-safety.js; npm pack --dry-run; openspec validate agent-codex-release-guardex-7-0-20-2026-04-22-12-12 --type change --strict; openspec validate --specs Not-tested: gx release and the GitHub npm workflow before merge
NagyVikt
deleted the
agent/codex/release-guardex-7-0-20-2026-04-22-12-12
branch
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).