Skip to content

feat: add dual publishing to npm and GitHub Packages#25

Merged
ramonclaudio merged 3 commits intomainfrom
feat/dual-publish-npm-github
Sep 7, 2025
Merged

feat: add dual publishing to npm and GitHub Packages#25
ramonclaudio merged 3 commits intomainfrom
feat/dual-publish-npm-github

Conversation

@ramonclaudio
Copy link
Owner

@ramonclaudio ramonclaudio commented Sep 7, 2025

Summary

  • Enable dual publishing to both npm and GitHub Packages registries
  • Add @rmncldyo/create-claude scoped package for GitHub Packages
  • Maintain all security features for both publishes

Changes

The workflow now publishes to both registries, providing users with installation flexibility.

Testing

  • Workflow will be tested on v0.1.11 release
  • Both registries will receive the same security artifacts

- Remove .intoto.jsonl file references (managed by GitHub internally)
- Simplify attestation signing logic
- Remove non-existent file patterns from release uploads
- Configure workflow to publish to both npm and GitHub Packages registries
- Add npm.pkg.github.com to allowed endpoints for security hardening
- Set up proper permissions including packages:write for GitHub Packages
- Update package name dynamically for scoped GitHub Packages publish
- Add installation instructions for both registries in release notes
- Maintain provenance and security artifacts for both publishes
- Document dual registry publishing feature
- Add GitHub Packages support details
- Include technical implementation notes
@ramonclaudio ramonclaudio merged commit 3984f3e into main Sep 7, 2025
6 checks passed
@ramonclaudio ramonclaudio deleted the feat/dual-publish-npm-github branch September 7, 2025 17:26
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