Skip to content

chore(ci): setup trusted publishing#475

Open
lwasser wants to merge 1 commit intoall-contributors:mainfrom
lwasser:deploy
Open

chore(ci): setup trusted publishing#475
lwasser wants to merge 1 commit intoall-contributors:mainfrom
lwasser:deploy

Conversation

@lwasser
Copy link
Member

@lwasser lwasser commented Mar 6, 2026

This pr closes #454

What:
I have done the following

  • on NPM i setup OIDC / Trusted Publishing and disabled tokens for the time being (safer)
  • Added a secure environment to the publish step (which is triggered on release) and added the maintainer team to have access to "approve" the final publish step. If we decide this is cumbersome, we can remove it.
  • Setup this action to run after tests but only on a release. We could have a totally separate deploy action if folks prefer that. i should i could use artifacts and such but it didn't work out quite the way i wanted it to.

How:

Checklist:

  • Documentation
  • Tests
  • Ready to be merged
  • Added myself to contributors table

@lwasser lwasser requested a review from jdalrymple March 6, 2026 04:04
@lwasser lwasser marked this pull request as ready for review March 6, 2026 04:04
@lwasser lwasser added this to the Release 27.0 milestone Mar 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Setup release based build trigger and trusted publishing

2 participants