Release object store `0.12.3` (non breaking API) Release July 2025

[alamb]

Which part is this question about

• Part of [EPIC] Planned Release Schedule #392
• Follow on to Release object store 0.12.2 (non breaking API) May (was June), 2025 #307

Per release schedule we aim for2 months release:

Additional context

• See prior discussion Discuss: Release object store 0.12.0 (breaking) or 0.11.2 (non breaking API) around Dec 15, 2024 #306

Describe the solution you'd like

• Update version + make release notes:
• Test with DataFusion: WIP: Update object_store 0.12.3 datafusion#16753
• Prepare release candidate + begin vote thread:
• Release to crates.io
• File tickets for next planned releases:

Community requested content:

• Retry requests when status code is 429 #410 (Release object store 0.13.1 (non breaking API) Release TDB 2025 #393 (comment))
• feat: retry on 408 #426 (Release object store 0.13.0 (breaking) - Target Nov 2025 #367 (comment))

[alamb]

@crepererum and I discussed this today.

Plan:

1. @crepererum will create a a 0.12.3 release branch by backporting the relevant non breaking changes to a new branch (rather than reverting on main)
2. I will run the release process

cc @paraseba and @criccomini and @tustvold

[crepererum]

I've created a branch release/0.12 based of the tag 0.12.2. I'll file a "backports PR" into that branch with picks the relevant changes from branch main. So the backport will look roughly like this:

gitGraph TB:
    commit id: "minor-1"
    commit id: "minor-2" tag: "v0.12.2" type: HIGHLIGHT
    branch "release/0.12"
    checkout "main"
    commit id: "minor-3"
    commit id: "major-1"
    commit id: "minor-4"
    commit id: "minor-5"
    commit id: "major-2"
    checkout "release/0.12"
    cherry-pick id: "minor-3" tag: ""
    cherry-pick id: "minor-4" tag: ""
    cherry-pick id: "minor-5" tag: "v0.12.3"

Loading

[alamb]

I've created a branch release/0.12 based of the tag 0.12.2. I'll file a "backports PR" into that branch with picks the relevant changes from branch main. So the backport will look roughly like this:

Sounds like a good plan to me -- once you complete this process, I'll make a release candidate from that branch (and will update the documentation in this repo to reflect that process)

Would you like help creating the backports or do you plan to do it yourself?

[crepererum]

I'm on it.

Edit: Done #433 . Needs release notes though, will do after backport PR is merged.

[crepererum]

Everything on the release/0.12 is now ready. The tag needs to be set and candidate + vote needs to be done. @alamb if you have a minute, could you take care of that?