feat: add npm trusted publishing with OIDC authentication#71
Open
feat: add npm trusted publishing with OIDC authentication#71
Conversation
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
There was a problem hiding this comment.
Pull request overview
This PR introduces automated npm package publishing using OIDC-based trusted publishing, eliminating the need for long-lived npm authentication tokens stored in GitHub secrets.
Changes:
- Added a new GitHub Actions workflow that publishes to npm on pushes to the main branch
- Configured OIDC authentication for secure, token-free publishing
- Enabled automatic provenance attestation generation for published packages
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Success criteria
How to test
CognigySocketClientpublish.ymlSecurity
Additional considerations
Documentation Considerations
These are hints for the documentation team to help write the docs.