chore(release-automation): activate release-plz, retire bespoke tooling, add OIDC scaffolding#379
Merged
Conversation
Polars 0.54.4 on crates.io resolved the chrono conflict that blocked release-plz's cargo package step, so the bespoke version-bump machinery can finally be retired. Deleted: - build/update_all_versions.rs (1157 lines) - .github/workflows/auto-tag-release.yml (168 lines) - scripts/ci/ci-pipeline.rs (thin wrapper, REMOVE-AFTER v0.5.73 met) - increment_version()/version_bump() from version.rs - STEP_VERSION_INCREMENT from workflow.rs Modified: - .gitignore: restored blanket build/ ignore (carve-out removed) - version.rs: dropped now-unfulfilled print_stdout expectation - ship.rs/phases.rs: removed version step, fixed completion messages - justfile recipes: version-bump retired, quick-deploy renumbered R4: activated release-plz push trigger + workflow_dispatch bridge to release.yml R7: added dormant OIDC publish job (if: false) for crates.io trusted publishing See docs/architecture/release-automation-plan.md §R4, §R5, §R7
githubrobbi
changed the title
This was referenced Jun 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes release automation loose ends from
docs/architecture/release-automation-plan.md.Summary
push: branches: [main]trigger)if: false)Why now
Polars 0.54.4 landed on crates.io (PR #378), resolving the chrono conflict that blocked release-plz's
cargo package --workspacestep. This unblocks the entire R4/R5 chain.Deleted
build/update_all_versions.rs(1157 lines).github/workflows/auto-tag-release.yml(168 lines)scripts/ci/ci-pipeline.rs(thin wrapper, REMOVE-AFTER v0.5.73 met)increment_version()/version_bump()from version.rsSTEP_VERSION_INCREMENTfrom workflow.rsModified
.gitignore: restored blanketbuild/ignore.github/workflows/release-plz.yml: push trigger + workflow_dispatch bridge + OIDC jobversion.rs: dropped now-unfulfilled print_stdout expectationship.rs/phases.rs: removed version step, fixed completion messagesrelease-automation-plan.md: dashboard R4🟢 R5🟢 R7🟡Verification
cargo clippy --workspace --all-targets -- -D warnings: ✅ 0 warningscargo fmt --check: ✅Remaining
See
docs/architecture/release-automation-plan.md§R4, §R5, §R7