Skip to content

Commit 41c7d29

Browse files
NagyViktNagyVikt
andauthored
Cut a fresh publishable Guardex release after npm lagged (#390)
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 Co-authored-by: NagyVikt <nagy.viktordp@gmail.com>
1 parent f9d2c7b commit 41c7d29

4 files changed

Lines changed: 24 additions & 3 deletions

File tree

README.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -689,6 +689,11 @@ npm pack --dry-run
689689
<details>
690690
<summary><strong>v7.x</strong></summary>
691691

692+
### v7.0.26
693+
- Bumped `@imdeadpool/guardex` from `7.0.25` to `7.0.26` so npm can publish a fresh version after `v7.0.25` reached GitHub Releases while the registry stayed on `7.0.24`.
694+
- README now documents both `npx skills add recodeee/` and `npx skills add recodeee/gitguardex`, and explains why the picker shows `gitguardex` instead of a separate `guardex` skill.
695+
- Keep the release scoped to version metadata plus the already-merged README installer guidance on `main`; no additional CLI/runtime behavior changed in this lane.
696+
692697
### v7.0.25
693698
- Bumped `@imdeadpool/guardex` from `7.0.24` to `7.0.25` so npm and GitHub Releases can ship the current `main` payload.
694699
- The bundled `GitGuardex Active Agents` VS Code companion now self-heals stale repo-scan ignore settings in older repos, keeps plain managed sandboxes visible in Source Control, and preserves cleanup truth so the tree matches actual sandbox state.
Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
# agent-codex-release-7-0-26-2026-04-23-16-21 (minimal / T1)
2+
3+
Branch: `agent/codex/release-7-0-26-2026-04-23-16-21`
4+
5+
Release-only lane: bump `@imdeadpool/guardex` to `7.0.26`, add the matching `README.md` release note entry, merge, and cut the GitHub release so publish automation can retry from a fresh semver after `v7.0.25` reached GitHub while npm still reported `7.0.24`.
6+
7+
## Handoff
8+
9+
- Handoff: change=`agent-codex-release-7-0-26-2026-04-23-16-21`; branch=`agent/codex/release-7-0-26-2026-04-23-16-21`; scope=`package.json, package-lock.json, README.md release notes`; action=`continue this sandbox, verify release-only metadata changes, then finish cleanup and cut GitHub release v7.0.26`.
10+
- Copy prompt: Continue `agent-codex-release-7-0-26-2026-04-23-16-21` on branch `agent/codex/release-7-0-26-2026-04-23-16-21`. Work inside the existing sandbox, review `openspec/changes/agent-codex-release-7-0-26-2026-04-23-16-21/notes.md`, continue from the current state instead of creating a new sandbox, and when the work is done run `gx branch finish --branch agent/codex/release-7-0-26-2026-04-23-16-21 --base main --via-pr --wait-for-merge --cleanup`.
11+
12+
## Cleanup
13+
14+
- [ ] Run: `gx branch finish --branch agent/codex/release-7-0-26-2026-04-23-16-21 --base main --via-pr --wait-for-merge --cleanup`
15+
- [ ] Record PR URL + `MERGED` state in the completion handoff.
16+
- [ ] Confirm sandbox worktree is gone (`git worktree list`, `git branch -a`).

package-lock.json

Lines changed: 2 additions & 2 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

package.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
{
22
"name": "@imdeadpool/guardex",
3-
"version": "7.0.25",
3+
"version": "7.0.26",
44
"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.",
55
"license": "MIT",
66
"preferGlobal": true,

0 commit comments

Comments
 (0)