Commit b03c8bc
committed
test(ci): bypass proto shims to test OIDC compatibility
This PR tests if npm OIDC works when we bypass proto/moonrepo shims entirely.
Changes:
- Replace moonrepo/setup-toolchain with actions/setup-node
- Install npm 11.6.2 directly (no proto shim)
- Install pnpm 10.17.1 directly (no proto shim)
- Install moon 1.39.1 directly (no proto shim)
- Keep GarthDB/changesets-action@v1.6.8 with oidcAuth: true
Purpose:
After exhaustive testing (v1.6.4-v1.6.8, PR #687), we've confirmed:
✅ OIDC environment variables ARE present in GitHub Actions
✅ npm 11.6.2 is the correct version
✅ Trusted publishers are configured correctly
❌ npm can't authenticate through proto shim chain
This test will definitively show if proto shims are the blocker.
Expected outcomes:
If this WORKS (✅ npm publishes successfully):
→ Proto shims are confirmed as the issue
→ We have two options:
1. Use this direct install approach (no proto in release workflow)
2. File bug with proto/moonrepo about OIDC support
If this FAILS (❌ still ENEEDAUTH):
→ Something else is wrong with OIDC setup
→ Fall back to NPM_TOKEN
Related:
- All v1.6.x attempts: ENEEDAUTH with proto
- PR #687: Confirmed OIDC vars present in shell
- PR #688: v1.6.8 still failed with proto1 parent 00c4198 commit b03c8bc
1 file changed
+10
-4
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
19 | 19 | | |
20 | 20 | | |
21 | 21 | | |
22 | | - | |
| 22 | + | |
| 23 | + | |
23 | 24 | | |
24 | | - | |
25 | | - | |
| 25 | + | |
| 26 | + | |
| 27 | + | |
| 28 | + | |
| 29 | + | |
| 30 | + | |
| 31 | + | |
26 | 32 | | |
27 | 33 | | |
28 | 34 | | |
| |||
31 | 37 | | |
32 | 38 | | |
33 | 39 | | |
34 | | - | |
| 40 | + | |
35 | 41 | | |
36 | 42 | | |
0 commit comments