From 9a7b8d76c9b2e0551f1e1429df3c73a0efdcb643 Mon Sep 17 00:00:00 2001 From: NagyVikt Date: Sat, 11 Apr 2026 19:37:41 +0200 Subject: [PATCH] Unblock npm publish by advancing package version past 5.0.0 The previous publish attempt failed because version 5.0.0 already exists on npm. This bumps @imdeadpool/guardex to 5.0.1 in both manifest and lockfile so release can proceed without overwriting an immutable published version. Constraint: npm does not allow re-publishing an existing version Rejected: Force-publish 5.0.0 again | npm rejects immutable version reuse Confidence: high Scope-risk: narrow Reversibility: clean Directive: Keep package.json and package-lock.json version fields aligned for each release bump Tested: npm test (54/54) Not-tested: Live npm publish for 5.0.1 in this commit step --- package-lock.json | 4 ++-- package.json | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/package-lock.json b/package-lock.json index a4579b4..b388663 100644 --- a/package-lock.json +++ b/package-lock.json @@ -1,12 +1,12 @@ { "name": "@imdeadpool/guardex", - "version": "5.0.0", + "version": "5.0.1", "lockfileVersion": 3, "requires": true, "packages": { "": { "name": "@imdeadpool/guardex", - "version": "5.0.0", + "version": "5.0.1", "license": "MIT", "bin": { "guardex": "bin/multiagent-safety.js", diff --git a/package.json b/package.json index f1079ce..538f9bd 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "@imdeadpool/guardex", - "version": "5.0.0", + "version": "5.0.1", "description": "GuardeX: the Guardian T-Rex for your repo, with hardened multi-agent git guardrails.", "license": "MIT", "preferGlobal": true,