Skip to content

Switch to OIDC Trusted Publishers#71

Merged
pipedrive-public-gha-bot[bot] merged 1 commit into
masterfrom
CICDL-258-oidc-trusted-publishers
May 22, 2026
Merged

Switch to OIDC Trusted Publishers#71
pipedrive-public-gha-bot[bot] merged 1 commit into
masterfrom
CICDL-258-oidc-trusted-publishers

Conversation

@Moser-ss
Copy link
Copy Markdown
Contributor

Switch npm publishing from token-based auth to OIDC Trusted Publishers. Also upgrades .nvmrc to Node 24 (npm 11.x required for OIDC).

Changes

  • .github/workflows/cicd_npm-publish.yml: add use_trusted_publisher: true, permissions block, extend supported_versions to [22,24]
  • .nvmrc: bump from 22 to 24

Manual follow-up required

  • Task 5: Verify Pipedrive Public GHA Bot has repo access
  • Task 6: Configure Trusted Publisher on npmjs.org (UI only)
  • Task 7: E2E validation after merge

Generated with Claude Code

…to Node 24

Node 24 ships npm 11.x which is required for OIDC Trusted Publishers (npm 10.x
in Node 22 does not support it). Adds permissions block and use_trusted_publisher
flag to the publish workflow; supported_versions extended to [22,24].

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@Moser-ss Moser-ss requested review from a team as code owners May 21, 2026 21:49
contents: write
with:
revision: ${{ github.event.pull_request.head.ref }}
supported_versions: '[22]'
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

In .nvmrc the Node version was set to 24. Is it correct that here it stays unchanged? Also, in package.json the version is still set to >=22 (yes, the 24 is covered :), but would it make sense to change it there as well?)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

With this setup, the publish workflow runs the tests with version 24 (main version based on the .nvmrc) and runs with version 22, which respects the package.json

@Moser-ss Moser-ss added the npm-version-minor used for deployment label May 22, 2026
@Moser-ss Moser-ss added the npm-ready-for-publish used for deployment label May 22, 2026
pipedrive-public-gha-bot Bot pushed a commit that referenced this pull request May 22, 2026
@pipedrive-public-gha-bot pipedrive-public-gha-bot Bot merged commit 163f91b into master May 22, 2026
7 checks passed
@pipedrive-public-gha-bot pipedrive-public-gha-bot Bot deleted the CICDL-258-oidc-trusted-publishers branch May 22, 2026 10:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

npm-ready-for-publish used for deployment npm-version-minor used for deployment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants