Skip to content

Add GitHub Packages publish for @paladini/mcp-me - #14

Merged
paladini merged 1 commit into
mainfrom
feat/github-packages-publish
Jul 23, 2026
Merged

Add GitHub Packages publish for @paladini/mcp-me#14
paladini merged 1 commit into
mainfrom
feat/github-packages-publish

Conversation

@paladini

Copy link
Copy Markdown
Owner

Summary

  • Adds a github-packages job to the existing Publish workflow that publishes @paladini/mcp-me to https://npm.pkg.github.com with --access public (same tag triggers as today).
  • Leaves the npmjs / MCP Registry / GitHub Release publish job behavior intact: same steps, gated to tag pushes only via if: github.event_name == 'push'.
  • Adds workflow_dispatch that runs only the GitHub Packages job, so the current version can land on the Packages tab without touching npmjs.

Test plan

  • Review .github/workflows/publish.yml: publish job steps match previous behavior aside from the tag-only if.
  • After merge: Actions → Publish → Run workflow on main to publish current package.json version to GitHub Packages only.
  • Confirm @paladini/mcp-me appears at https://github.com/paladini?tab=packages and is public.
  • On next version tag vX.Y.Z, confirm both npmjs mcp-me and GH Packages @paladini/mcp-me publish as expected.

Extend the Publish workflow with a separate github-packages job and workflow_dispatch that publishes only to npm.pkg.github.com, leaving the npmjs/MCP Registry/release path unchanged for tag pushes.
@paladini
paladini merged commit 7f2f0fd into main Jul 23, 2026
2 checks passed
@paladini
paladini deleted the feat/github-packages-publish branch July 23, 2026 22:45
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