From d44e45aff50d5a0fdfe902936b7efb0ec6f7877d Mon Sep 17 00:00:00 2001 From: SentienceDEV Date: Sun, 15 Feb 2026 12:08:57 -0800 Subject: [PATCH] fix release to new org --- .github/workflows/release.yml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 07b906b..e1bd1d8 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -162,7 +162,9 @@ jobs: # npm v10 syntax: # - `npm access list packages ` checks whether the user can see/publish packages in that scope # - if you are not a member/owner of the npm org, this typically fails (403/404) which is what we want surfaced - npm access list packages @predicatesystems --registry https://registry.npmjs.org --json + # NOTE: Some orgs restrict org-wide package listing to admins/owners. + # Treat this as best-effort diagnostics; do not block publishing. + npm access list packages @predicatesystems --registry https://registry.npmjs.org --json || echo "WARN: cannot list org packages for @predicatesystems (may be restricted; continuing)" echo "" echo "=== Sanity: packages visible to current user ===" npm access list packages "$(npm whoami --registry https://registry.npmjs.org)" --registry https://registry.npmjs.org --json