Skip to content

Conversation

Andy-Grigg
Copy link
Contributor

Closes #598

Use Trusted Publisher instead of the previous token approach. I have defined an environment that:

  • Requires approval from one other member of the maintainer team
  • Only runs from a release/* branch

@Andy-Grigg Andy-Grigg requested a review from da1910 August 21, 2024 13:01
@github-actions github-actions bot added the maintenance Package and maintenance related label Aug 21, 2024
@Andy-Grigg Andy-Grigg added this pull request to the merge queue Aug 21, 2024
Copy link

codecov bot commented Aug 21, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.44%. Comparing base (1ab56f8) to head (914cd35).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #646   +/-   ##
=======================================
  Coverage   94.44%   94.44%           
=======================================
  Files           7        7           
  Lines         792      792           
=======================================
  Hits          748      748           
  Misses         44       44           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Merged via the queue into main with commit b62de12 Aug 21, 2024
@Andy-Grigg Andy-Grigg deleted the ci/use-trusted-publisher branch August 21, 2024 14:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

maintenance Package and maintenance related

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support 'Trusted Publisher' PyPI publishing

3 participants