Broken bump release flow

[Cedric / ViaDézo1er (viadezo1er)]

https://github.com/braintrustdata/bt/actions/workflows/release-bump-pr.yml
cargo update --workspace --offline crashed due to lack of cache, crashing the CI.
Replaces it with python.

I think commit e539dd8 is self-explanatory? Comments like #218 (comment) are badly formatted.

60a80b9 and 72e32ce fix potential issues that haven't happened yet.
Prevents having multiple release workflow running at once and publish the tag only after the build has been completed so we don't have empty tags with no associated binaries.

[github-actions]

Latest downloadable build artifacts for this PR commit 72e32ce07391:

• Workflow run: https://github.com/braintrustdata/bt/actions/runs/26857438904
• Download all artifacts (GitHub CLI): gh run download 26857438904 --repo braintrustdata/bt
• Installers are published from main automatically. To publish one for a PR branch, run release-canary manually via workflow_dispatch.

Available artifact names

• artifacts-build-global
• artifacts-build-local-x86_64-apple-darwin
• artifacts-build-local-aarch64-pc-windows-msvc
• artifacts-build-local-x86_64-pc-windows-msvc
• artifacts-build-local-aarch64-apple-darwin
• artifacts-build-local-x86_64-unknown-linux-gnu
• artifacts-build-local-x86_64-unknown-linux-musl
• artifacts-build-local-aarch64-unknown-linux-gnu
• artifacts-plan-dist-manifest
• cargo-dist-cache

[Cedric / ViaDézo1er (viadezo1er)]

I was the one who suggested cargo update --workflow --offline, but didn't know at the time it requires a warm cache since it still resolves all dependencies...

[Cedric / ViaDézo1er (viadezo1er)]

Comments are badly formatted, see the artifact names in #218 (comment).

[Cedric / ViaDézo1er (viadezo1er)]

We could push a tag then cancel the build step and have to manually delete the tag.

[Luca Forstner (lforst)]

can you quickly explain what was broken and how this PR fixes it?

[Cedric / ViaDézo1er (viadezo1er)]

https://github.com/braintrustdata/bt/actions/workflows/release-bump-pr.yml
cargo update --workspace --offline crashed due to lack of cache, crashing the CI.
Replaces it with python to update Cargo.lock.
I think I didn't notice it was broken because I was still bumping the Cargo.toml/lock version field and creating the release PRs manually.

I think commit e539dd8 is self-explanatory? Comments like #218 (comment) are badly formatted.

60a80b9 and 72e32ce fix potential issues that haven't happened yet.
Prevents having multiple release workflow running at once and publish the tag only after the build has been completed so we don't have empty tags with no associated binaries.