Skip to content

Conversation

@vtsvetkov-splunk
Copy link
Contributor

@vtsvetkov-splunk vtsvetkov-splunk commented Feb 19, 2025

Issue number:

PR Type

What kind of change does this PR introduce?

  • Feature
  • Bug Fix
  • Refactoring (no functional or API changes)
  • Documentation Update
  • Maintenance (dependency updates, CI, etc.)

Summary

  • The publish job is failed with an error
npm notice Publishing to https://registry.npmjs.org/ with tag latest and public access
npm error code EUSAGE
npm error Provenance generation in GitHub Actions requires "write" access to the "id-token" permission
npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2025-02-18T16_29_20_197Z-debug-0.log
  • It is now allowed to manually publish NPM package without a bump

Changes

  • Give permissions for NPM publish during a regular build
  • Add ability to publish version from the repository without a bump for a manual workflow

User experience

No changes

Checklist

If an item doesn't apply to your changes, leave it unchecked.

@vtsvetkov-splunk vtsvetkov-splunk marked this pull request as ready for review February 19, 2025 07:43
@vtsvetkov-splunk vtsvetkov-splunk requested a review from a team as a code owner February 19, 2025 07:43
@vtsvetkov-splunk vtsvetkov-splunk enabled auto-merge (squash) February 19, 2025 07:43
artemrys
artemrys previously approved these changes Feb 19, 2025
@vtsvetkov-splunk vtsvetkov-splunk merged commit c2efdc8 into develop Feb 19, 2025
126 checks passed
@vtsvetkov-splunk vtsvetkov-splunk deleted the feature/npm-publish branch February 19, 2025 09:37
@github-actions github-actions bot locked and limited conversation to collaborators Feb 19, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants