Skip to content

Prepare the next publishable Guardex npm patch release#325

Merged
NagyVikt merged 1 commit intomainfrom
agent/codex/release-guardex-7-0-22-2026-04-22-16-19
Apr 22, 2026
Merged

Prepare the next publishable Guardex npm patch release#325
NagyVikt merged 1 commit intomainfrom
agent/codex/release-guardex-7-0-22-2026-04-22-16-19

Conversation

@NagyVikt
Copy link
Copy Markdown
Collaborator

Automated by gx branch finish (PR flow).

main already contains post-7.0.21 operator-facing improvements, but the package metadata and README release history still stop at 7.0.21. This bumps the release metadata to 7.0.22 and adds the matching OpenSpec change so the next publish stays aligned with the verified main payload.

Constraint: Release lane must stay metadata-only against the already-merged main payload
Rejected: Ship without a new OpenSpec change | would leave the 7.0.22 finish lane without truthful task state
Rejected: Reuse the older 7.0.21 notes-only change | would hide the current 7.0.22 branch and verification evidence
Confidence: high
Scope-risk: narrow
Reversibility: clean
Directive: Keep future release-only bumps limited to version metadata and README/OpenSpec release history unless the payload itself changes
Tested: node --test test/metadata.test.js
Tested: node --check bin/multiagent-safety.js
Tested: npm pack --dry-run
Tested: openspec validate agent-codex-release-guardex-7-0-22-2026-04-22-16-19 --type change --strict
Tested: openspec validate --specs
Not-tested: gx release publish workflow
@NagyVikt NagyVikt merged commit b70134e into main Apr 22, 2026
@NagyVikt NagyVikt deleted the agent/codex/release-guardex-7-0-22-2026-04-22-16-19 branch April 22, 2026 14:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant