Skip to content

Conversation

@david-luna
Copy link
Member

PR to add provenance and trusted publishers to Elastic APM RUM packages. It also adds --ignore-scripts npm CLI option wherever possible.

Closes: #1644
Supersedes: #1489

@github-actions
Copy link

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

Copy link
Member

@v1v v1v left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, just a couple of changes:

  • to keep the least-permissive token access at the job level
  • to remove the NPM_TOKEN usage, trusted publishers won't use it

Comment on lines -25 to -27
permissions:
contents: read
id-token: write
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's keep this as is, we normally follow this pattern:

  • default top-level permissions as is
  • job permissions with finer-granularity

DRY_RUN: "${{ inputs.dry-run }}"
GITHUB_TOKEN: ${{ steps.get_token.outputs.token }}
run: |
echo "//registry.npmjs.org/:_authToken=${{ secrets.NPM_TOKEN }}" > .npmrc
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be removed too if we use the trusted publishers

Suggested change

@v1v
Copy link
Member

v1v commented Oct 29, 2025

@david-luna , If you need help with testing this PR, let me know, I recall I had some test packages to run on my forked repository:

so we could try it

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.

Use trusted publishers

3 participants