From eb0c0f5ad837f4f25f5b495de179681f96304c13 Mon Sep 17 00:00:00 2001 From: NagyVikt Date: Mon, 13 Apr 2026 20:34:57 +0200 Subject: [PATCH] Unblock npm publish with the next patch version The package and npm registry were both at 5.0.4, so publishing would conflict. This bumps the package to 5.0.5 and records the matching release-note entry so publish workflow and metadata checks stay aligned. Constraint: Keep README release notes in sync with package version for metadata guardrails Rejected: Publish 5.0.4 again | npm rejects duplicate published versions Confidence: high Scope-risk: narrow Reversibility: clean Directive: For every future version bump, update README release notes in the same change Tested: npm test Tested: npm pack --dry-run --- README.md | 4 ++++ package-lock.json | 4 ++-- package.json | 2 +- 3 files changed, 7 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 29f142a..de3c0f6 100644 --- a/README.md +++ b/README.md @@ -238,6 +238,10 @@ npm pack --dry-run ## Release notes +### v5.0.5 + +- Bumped package version from `5.0.4` to `5.0.5` so npm publish can proceed with the next patch release. + ### v5.0.4 - Bumped package version from `5.0.3` to `5.0.4` to stay one patch ahead of the current npm published version. diff --git a/package-lock.json b/package-lock.json index 92f6de1..f8cdf5f 100644 --- a/package-lock.json +++ b/package-lock.json @@ -1,12 +1,12 @@ { "name": "@imdeadpool/guardex", - "version": "5.0.4", + "version": "5.0.5", "lockfileVersion": 3, "requires": true, "packages": { "": { "name": "@imdeadpool/guardex", - "version": "5.0.4", + "version": "5.0.5", "license": "MIT", "bin": { "guardex": "bin/multiagent-safety.js", diff --git a/package.json b/package.json index 956b3fb..f964c2b 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "@imdeadpool/guardex", - "version": "5.0.4", + "version": "5.0.5", "description": "GuardeX: the Guardian T-Rex for your repo, with hardened multi-agent git guardrails.", "license": "MIT", "preferGlobal": true,