Skip to content

Fix release workflow for breaking changes in upload/download artifact#148

Merged
bdraco merged 1 commit intomasterfrom
fix_release_workflow
May 2, 2025
Merged

Fix release workflow for breaking changes in upload/download artifact#148
bdraco merged 1 commit intomasterfrom
fix_release_workflow

Conversation

@bdraco
Copy link
Member

@bdraco bdraco commented May 2, 2025

I also switched it over to trusted publishing since its already set up.

@codecov
Copy link

codecov bot commented May 2, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.60%. Comparing base (7feb3d0) to head (ba227f4).
Report is 1 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #148   +/-   ##
=======================================
  Coverage   92.60%   92.60%           
=======================================
  Files           3        3           
  Lines         311      311           
  Branches       24       24           
=======================================
  Hits          288      288           
  Misses         12       12           
  Partials       11       11           

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

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@bdraco bdraco merged commit dd81a93 into master May 2, 2025
32 of 45 checks passed
@bdraco bdraco deleted the fix_release_workflow branch May 2, 2025 18:24
needs: [build_wheels, build_sdist]
runs-on: ubuntu-latest
permissions:
contents: write # IMPORTANT: mandatory for making GitHub Releases
Copy link
Member

Choose a reason for hiding this comment

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

This privilege looks unused, FYI.

Copy link
Member Author

Choose a reason for hiding this comment

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

I wasn’t entirely sure whether we’re planning to stick with the GitHub release workflow or move toward just pushing tags, happy to align either way.

Copy link
Member

Choose a reason for hiding this comment

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

My typical workflow outside of aio-libs is a bit different, but also publishes to GH releases. I'd love to eventually migrate to that. But for now, whatever you're going to set up will be good.

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.

2 participants