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
5 changes: 5 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -672,6 +672,11 @@ npm pack --dry-run
<details>
<summary><strong>v7.x</strong></summary>

### v7.0.25
- Bumped `@imdeadpool/guardex` from `7.0.24` to `7.0.25` so npm and GitHub Releases can ship the current `main` payload.
- 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.
- Bumped the shipped Active Agents companion manifests from `0.0.8` to `0.0.9` so local VS Code installs can pick up the newer workspace build and show the refreshed extension version from this release.

### v7.0.24
- Bumped `@imdeadpool/guardex` from `7.0.23` to `7.0.24` so GitHub Releases and the npm publish retry can advance together after `v7.0.23` landed on GitHub but not on npm.
- Release verification no longer loses its base ref on tag-triggered runs, so the publish workflow keeps the history it needs before packing and publish checks.
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
## Why

- npm and GitHub Releases are both currently at `@imdeadpool/guardex@7.0.24`, so the next publishable patch version needs to advance before another release can be cut.
- `main` now includes more operator-facing Active Agents companion improvements than the current README release history records, so the release notes would drift again without a matching version bump.
- The shipped VS Code companion code changed after the last manifest bump, so the bundled extension version needs a fresh visible version for workspace auto-update and install verification.

## What Changes

- Bump the package release metadata from `7.0.24` to `7.0.25` in `package.json` and `package-lock.json`.
- Add a `README.md` release-notes entry for `v7.0.25` that calls out the shipped `GitGuardex Active Agents` VS Code companion improvements visible in Source Control.
- Bump `vscode/guardex-active-agents/package.json` and `templates/vscode/guardex-active-agents/package.json` from `0.0.8` to `0.0.9` so the bundled companion can surface the newer shipped build.

## Impact

- Unblocks the next npm package release and matching GitHub release without changing the Guardex CLI runtime beyond what is already merged on `main`.
- Keeps the package version, companion manifest version, and README release history aligned so release state stays trustworthy to operators using the VS Code surface.
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
## ADDED Requirements

### Requirement: Release metadata and bundled companion version alignment

The release metadata SHALL move to the next publishable Guardex package version when maintainers intentionally request the next npm release after the current published Guardex version, and any bundled Active Agents companion version exposed by that release SHALL be recorded alongside it.

#### Scenario: Prepare the next publishable npm patch release with companion-visible notes

- **GIVEN** the current Guardex package version is already the latest published release metadata in the repo and npm registry
- **AND** the shipped repo contains newer Active Agents companion changes that operators should see called out in the next release
- **WHEN** maintainers request the next npm version bump
- **THEN** `package.json` and `package-lock.json` SHALL be bumped to the next publishable semver
- **AND** `README.md` SHALL record the new release version with the shipped Active Agents companion improvements
- **AND** the live/template Active Agents manifests SHALL expose the companion version bundled by that release.
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
## Handoff

- Handoff: change=`agent-codex-release-guardex-7-0-25-2026-04-23-12-33`; branch=`agent/codex/release-guardex-7-0-25-2026-04-23-12-33`; scope=`package.json`, `package-lock.json`, `README.md`, `vscode/guardex-active-agents/package.json`, `templates/vscode/guardex-active-agents/package.json`; action=`bump Guardex to v7.0.25, bump the bundled Active Agents companion to 0.0.9, and cut a release that explicitly calls out the VS Code extension surface`.

## 1. Specification

- [x] 1.1 Finalize proposal scope and acceptance criteria for `agent-codex-release-guardex-7-0-25-2026-04-23-12-33`.
- [x] 1.2 Define normative requirements in `specs/release-version-bump/spec.md`.

## 2. Implementation

- [x] 2.1 Bump `package.json`, `package-lock.json`, `README.md`, and the live/template Active Agents companion manifests to the next publishable release versions.
- [x] 2.2 Keep the release scoped to metadata and packaged companion versioning only; no new Guardex runtime behavior is introduced in this lane.

## 3. Verification

- [x] 3.1 Run `npm test`. The full suite passed in this lane with `249` tests, `248` passes, `1` skip, and `0` failures.
- [x] 3.2 Run `node --check bin/multiagent-safety.js` and `npm pack --dry-run`. Both passed, and `npm pack --dry-run` produced `imdeadpool-guardex-7.0.25.tgz`.
- [x] 3.3 Run `openspec validate agent-codex-release-guardex-7-0-25-2026-04-23-12-33 --type change --strict` and `openspec validate --specs`. The change validated cleanly, and repo-level spec validation exited clean with `No items found to validate.`

## 4. Cleanup

- [ ] 4.1 Run `gx branch finish --branch agent/codex/release-guardex-7-0-25-2026-04-23-12-33 --base main --via-pr --wait-for-merge --cleanup`.
- [ ] 4.2 Record PR URL + final `MERGED` state in the completion handoff.
- [ ] 4.3 Confirm sandbox cleanup with `git worktree list` and `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.24",
"version": "7.0.25",
"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
2 changes: 1 addition & 1 deletion templates/vscode/guardex-active-agents/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
"displayName": "GitGuardex Active Agents",
"description": "Shows live Guardex sandbox sessions and repo changes inside VS Code Source Control.",
"publisher": "recodeee",
"version": "0.0.8",
"version": "0.0.9",
"license": "MIT",
"icon": "icon.png",
"engines": {
Expand Down
2 changes: 1 addition & 1 deletion vscode/guardex-active-agents/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
"displayName": "GitGuardex Active Agents",
"description": "Shows live Guardex sandbox sessions and repo changes inside VS Code Source Control.",
"publisher": "recodeee",
"version": "0.0.8",
"version": "0.0.9",
"license": "MIT",
"icon": "icon.png",
"engines": {
Expand Down