From fbbaba7a3aed4438ba3ee311680c97b4280189fd Mon Sep 17 00:00:00 2001 From: NagyVikt Date: Sat, 11 Apr 2026 13:34:41 +0200 Subject: [PATCH] Restore npm release workflow execution in the renamed repository The release pipeline was silently skipped because the workflow guard still targeted the old repository slug. Updating the guard to recodeecom/musafety ensures tagged releases can actually run publish with provenance. Constraint: Keep release workflow restricted to the canonical maintainer repo Rejected: Remove repository guard entirely | risks unintended publish attempts from forks Confidence: high Scope-risk: narrow Reversibility: clean Directive: If repository slug changes again, update both workflow guard and release tests together Tested: npm test (41/41 pass) Not-tested: live npm publish success from GitHub Actions with npm environment secrets --- .github/workflows/release.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index c48474f..e4e37e5 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -14,7 +14,7 @@ permissions: jobs: publish: - if: github.repository == 'recodeecom/multiagent-safety' + if: github.repository == 'recodeecom/musafety' runs-on: ubuntu-latest environment: npm