Skip to content

fix: configure scoped registry auth for release workflow#18

Merged
peter-svensson merged 1 commit intomainfrom
fix/release-registry-auth
Mar 13, 2026
Merged

fix: configure scoped registry auth for release workflow#18
peter-svensson merged 1 commit intomainfrom
fix/release-registry-auth

Conversation

@peter-svensson
Copy link
Copy Markdown
Member

Summary

  • Release workflow set the npm auth token but didn't map the @sparetimecoders scope to GitHub Packages
  • bun install failed with 401 fetching @sparetimecoders/messaging
  • Use the same bunfig.toml approach as ci.yml

Test plan

  • Merge and re-trigger the v0.0.2 release

🤖 Generated with Claude Code

The release workflow only set the npm auth token in ~/.npmrc without
mapping the @sparetimecoders scope to GitHub Packages. This caused
bun install to fail with a 401 when fetching @sparetimecoders/messaging.

Use the same bunfig.toml approach as ci.yml to set both the scope
registry URL and auth token.
@peter-svensson peter-svensson enabled auto-merge (squash) March 13, 2026 13:52
@peter-svensson peter-svensson disabled auto-merge March 13, 2026 13:53
@peter-svensson peter-svensson merged commit c757151 into main Mar 13, 2026
4 checks passed
@peter-svensson peter-svensson deleted the fix/release-registry-auth branch March 13, 2026 13:53
@codecov
Copy link
Copy Markdown

codecov Bot commented Mar 13, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

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