Skip to content

fix(ci): OIDC publish without NPM_TOKEN - #563

Merged
cobusgreyling merged 1 commit into
mainfrom
fix/oidc-publish-no-token
Aug 28, 2026
Merged

fix(ci): OIDC publish without NPM_TOKEN#563
cobusgreyling merged 1 commit into
mainfrom
fix/oidc-publish-no-token

Conversation

@cobusgreyling

Copy link
Copy Markdown
Owner

Retry path for loop 0.2.0 / loop-init 1.7.0 / loop-audit 1.9.0. Trusted publisher OIDC cannot run while NODE_AUTH_TOKEN is set.

NPM_TOKEN still 404s. If the packages now have a GitHub Actions
trusted publisher, NODE_AUTH_TOKEN would override OIDC and keep failing.
@github-actions

Copy link
Copy Markdown
Contributor

This PR changes paths that must run the real validate and audit workflows (tools, patterns, scripts, or CI).

Fork PRs from first-time contributors start with those workflows waiting for approval. A maintainer needs to open the Checks tab and click Approve and run workflows. Until that happens, branch protection will show the PR as blocked even after a review.

Content-only PRs (docs/, examples/, stories/, skills/, root markdown) skip this step — required checks are posted from this workflow instead.

— loop-engineering fork-pr-gate

@github-actions

Copy link
Copy Markdown
Contributor

Loop Readiness Audit

Score: 100/100 (L3)

Strong loop readiness — good candidate for L3 with explicit gates.

Top suggestions

  • Run the loop and commit changelog-drafter-state.md (or append loop-run-log.md) so Loop Ready can see a fresh timestamp
  • Scaffold a harness: npx @cobusgreyling/loop-init . --with-foundry (or npx @cobusgreyling/harness-foundry init --from loop-engineering:daily-triage)
  • Scaffold memory tiers: npx @cobusgreyling/loop-init . --with-memory
  • Scaffold a fleet: npx @cobusgreyling/loop-init . --with-fleet

Posted by audit.yml · loop-audit docs

@cobusgreyling
cobusgreyling merged commit d56d1e6 into main Aug 28, 2026
3 checks passed
@cobusgreyling
cobusgreyling deleted the fix/oidc-publish-no-token branch August 28, 2026 10:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant