You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Remove scoped package name (@mearman/mcp-template) from package.json
- Remove publishConfig pointing to GitHub Packages registry
- Update semantic-release to disable npm publishing (npmPublish: false)
- Remove GitHub Packages registry from semantic-release workflow
- Add separate GitHub Packages publishing step after semantic-release
- Remove NPM publishing from release workflow (template only publishes to GitHub Packages)
The issue was that semantic-release was trying to publish a scoped package
directly to GitHub Packages, which requires different permissions. Following
the pattern from mcp-wayback-machine, we now:
1. Keep an unscoped name in package.json
2. Let semantic-release handle versioning without publishing to npm
3. Publish to GitHub Packages in a separate step with the scoped name
0 commit comments