Skip to content

fix release to new org #196

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rcholic merged 1 commit into from
Feb 15, 2026
+3 −1
Merged

fix release to new org #196

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 3 additions & 1 deletion .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -162,7 +162,9 @@ jobs:
# npm v10 syntax:
# - `npm access list packages <scope>` 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
Expand Down
Loading