From 097545529a8c7b6da7bebe77c2e86606cdbea49a Mon Sep 17 00:00:00 2001 From: NagyVikt Date: Wed, 22 Apr 2026 15:14:39 +0200 Subject: [PATCH] Publish a fresh npm version for the current verified release payload This bumps package.json to 7.0.21 and adds the matching README release-notes entry so gx release can cut the next GitHub release from the current merged mainline. The branch starter skipped the T1 scaffold, so the notes-only OpenSpec change was recreated in the announced path before commit. Constraint: Release automation publishes from GitHub release events and requires package metadata plus README release notes to stay aligned Rejected: Reuse 7.0.20 without a bump | npm will not republish an existing version Confidence: high Scope-risk: narrow Reversibility: clean Directive: Future package releases must bump package.json and prepend the matching README release-notes heading in the same change Tested: node --test test/metadata.test.js test/release.test.js; npm pack --dry-run; openspec validate --specs Not-tested: Live GitHub release creation and npm publish before merge --- README.md | 5 +++++ .../.openspec.yaml | 2 ++ .../notes.md | 5 +++++ package.json | 2 +- 4 files changed, 13 insertions(+), 1 deletion(-) create mode 100644 openspec/changes/agent-codex-bump-npm-version-to-7-0-21-and-prepare-r-2026-04-22-15-11/.openspec.yaml create mode 100644 openspec/changes/agent-codex-bump-npm-version-to-7-0-21-and-prepare-r-2026-04-22-15-11/notes.md diff --git a/README.md b/README.md index 1c4243b..b30a01c 100644 --- a/README.md +++ b/README.md @@ -647,6 +647,11 @@ npm pack --dry-run
v7.x +### v7.0.21 +- Bumped `@imdeadpool/guardex` from `7.0.20` to `7.0.21` so npm can publish the next release from the current merged mainline. +- Keep the release scoped to version and release metadata only; the package payload stays the same as the verified `main` branch contents. +- Published-release automation will pick up this new package version once the matching GitHub release is created. + ### v7.0.20 - The VS Code Active Agents tree now exposes worktree-owned SCM changes and lock ownership directly, so operators can see which sandbox owns a dirty file before they act. - Guardex now keeps merged cleanup evidence truthful by recording final cleanup proof only after the merge and cleanup state is actually available. diff --git a/openspec/changes/agent-codex-bump-npm-version-to-7-0-21-and-prepare-r-2026-04-22-15-11/.openspec.yaml b/openspec/changes/agent-codex-bump-npm-version-to-7-0-21-and-prepare-r-2026-04-22-15-11/.openspec.yaml new file mode 100644 index 0000000..25345f4 --- /dev/null +++ b/openspec/changes/agent-codex-bump-npm-version-to-7-0-21-and-prepare-r-2026-04-22-15-11/.openspec.yaml @@ -0,0 +1,2 @@ +schema: spec-driven +created: 2026-04-22 diff --git a/openspec/changes/agent-codex-bump-npm-version-to-7-0-21-and-prepare-r-2026-04-22-15-11/notes.md b/openspec/changes/agent-codex-bump-npm-version-to-7-0-21-and-prepare-r-2026-04-22-15-11/notes.md new file mode 100644 index 0000000..2edc260 --- /dev/null +++ b/openspec/changes/agent-codex-bump-npm-version-to-7-0-21-and-prepare-r-2026-04-22-15-11/notes.md @@ -0,0 +1,5 @@ +# T1 Notes + +- Bump `@imdeadpool/guardex` from `7.0.20` to `7.0.21` so npm can accept the next publish from the already-verified `main` payload. +- Update the README release notes in the same change so the release history stays aligned with the package metadata. +- Keep the release narrowly scoped to metadata only; no package payload changes are intended in this bump. diff --git a/package.json b/package.json index b0e1043..bf4dc2e 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "@imdeadpool/guardex", - "version": "7.0.20", + "version": "7.0.21", "description": "Guardian T-Rex for your multi-agent repo. Isolated worktrees, file locks, and PR-only merges stop parallel Codex & Claude agents from overwriting each other's work. Auto-wires Oh My Codex, Oh My Claude, OpenSpec, and Caveman.", "license": "MIT", "preferGlobal": true,