Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -266,6 +266,12 @@ Being honest about where this still has issues:
<details open>
<summary><strong>v7.x</strong></summary>

### v7.0.39
- Bumped `@imdeadpool/guardex` from `7.0.38` to `7.0.39` so the current
`main` payload can publish under a fresh npm version after `7.0.38` reached
the registry.
- No new CLI command behavior is introduced in this release lane.

### v7.0.38
- Bumped `@imdeadpool/guardex` from `7.0.37` to `7.0.38` so the current
`main` payload can publish under a fresh npm version after `7.0.37` reached
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
schema: spec-driven
created: 2026-04-27
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
# agent-codex-bump-guardex-to-7-0-39-release-2026-04-27-18-38 (minimal / T1)

Branch: `agent/codex/bump-guardex-to-7-0-39-release-2026-04-27-18-38`

Ship the next Guardex npm patch release by bumping `@imdeadpool/guardex`
from `7.0.38` to `7.0.39`, adding the matching README release note, and
cutting the matching GitHub release after the release branch merges.

Scope:
- Update `package.json` and `package-lock.json` to `7.0.39`.
- Add the `v7.0.39` README release note.
- Verify the package metadata and tarball before finish.
- Finish through PR merge, sandbox cleanup, and GitHub release creation.

Verification:
- `npm test`
- `node --check bin/multiagent-safety.js`
- `npm pack --dry-run`

## Handoff

- Handoff: change=`agent-codex-bump-guardex-to-7-0-39-release-2026-04-27-18-38`; branch=`agent/codex/bump-guardex-to-7-0-39-release-2026-04-27-18-38`; scope=`package.json, package-lock.json, README.md, openspec/changes/agent-codex-bump-guardex-to-7-0-39-release-2026-04-27-18-38/*`; action=`finish this sandbox via PR merge + cleanup, then create GitHub release v7.0.39`.
- Copy prompt: Continue `agent-codex-bump-guardex-to-7-0-39-release-2026-04-27-18-38` on branch `agent/codex/bump-guardex-to-7-0-39-release-2026-04-27-18-38`. Work inside the existing sandbox, review `openspec/changes/agent-codex-bump-guardex-to-7-0-39-release-2026-04-27-18-38/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/bump-guardex-to-7-0-39-release-2026-04-27-18-38 --base main --via-pr --wait-for-merge --cleanup`, then create GitHub release `v7.0.39`.

## Cleanup

- [ ] Run: `gx branch finish --branch agent/codex/bump-guardex-to-7-0-39-release-2026-04-27-18-38 --base main --via-pr --wait-for-merge --cleanup`
- [ ] Record PR URL + `MERGED` state in the completion handoff.
- [ ] Create or update GitHub release `v7.0.39`.
- [ ] Confirm sandbox worktree is gone (`git worktree list`, `git branch -a`).
4 changes: 2 additions & 2 deletions package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@imdeadpool/guardex",
"version": "7.0.38",
"version": "7.0.39",
"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,
Expand Down