Release object_store 0.12.0 (API breaking) Around Feb 30 2025

[alamb]

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
Per @tustvold on

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

and then do a breaking release late February in advance of the scheduled March breaking arrow release

Previous release:

• Release object store 0.11.2 (non API breaking) Around Dec 15 2024 #6902

Describe the solution you'd like
Let's plan for a major release

• Update version + make release notes
• Prepare release candidate + begin vote thread
• Release to crates.io

Items to potentially resolve

• Decouple ObjectStore from Reqwest #7183
• chore: enable conditional put by default for S3 #7181
• feat: add Extensions to object store GetOptions #7170
• [Discussion] Object Store Composition #7171

Describe alternatives you've considered

Additional context
See discussion on #6596

[alamb]

I plan to assemble a release candidate for this release later in the week or early next week

[tustvold]

I think it would be good to try to get the following into this release if possible:

• Decouple ObjectStore from Reqwest #7183
• chore: enable conditional put by default for S3 #7181
• feat: add Extensions to object store GetOptions #7170 (if we go down that path)

[Xuanwo]

Hi, I personally hope we can hold off on #7170 until we resolve #7171.

Alternatively, we could implement this feature in http::Extension by DF, as mentioned by @tustvold, which wouldn't require changing the object_store API. This way, the changes would be scoped only to DF. From my current understanding, DF is the only producer and user of the proposed extensions, such as tracing spans.

[alamb]

Thanks @tustvold and @Xuanwo -- I have added those items to the list on this ticket