-
Notifications
You must be signed in to change notification settings - Fork 3
feat: add npm trusted publishing with OIDC authentication #71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Success criteria
How to test
CognigySocketClientpublish.ymlSecurity
Additional considerations
Documentation Considerations
These are hints for the documentation team to help write the docs.