-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Labels
internalA refactor or improvement that is not user-facingA refactor or improvement that is not user-facing
Description
For consistency/idempotency/recovery purposes, we want to enforce a consistent order in our publish steps during uv releases. Right now all of our publish workflows (which are reusable workflows) get scheduled in parallel, and race to win.
This is because we have the following in our dist configuration:
publish-jobs = ["./publish-pypi", "./publish-crates"]Instead, we should probably do:
publish-jobs = ["./publish"]...where publish.yml is a reusable workflow that then dispatches to publish-pypi.yml and publish-crates.yml in an ordered manner.
In effect, our stagger would be:
release.yml
|
\__ publish.yml
|
\__
\ publish-pypi.yml
|
\ publish-crates.yml
Metadata
Metadata
Assignees
Labels
internalA refactor or improvement that is not user-facingA refactor or improvement that is not user-facing