Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Nov 9, 2025

This PR contains the following updates:

Package Type Update Change
pyo3-bytes dependencies minor 0.3.0 -> 0.5.0

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

developmentseed/obstore (pyo3-bytes)

v0.5.0

Compare Source

New Features 🪄
Breaking changes 🔧
Object store methods

No breaking changes.

Store constructors
  • Removed S3Store.from_session and S3Store._from_native. Use credential providers instead.
  • Reduce the config variations supported for input. I.e. we previously allowed region, aws_region, REGION or AWS_REGION as a config parameter to S3Store, which could make it confusing. We now only support a single config input value for each underlying concept. #​323
Fsspec
Bug fixes 🐛
Documentation 📖
New Contributors

Full Changelog: developmentseed/obstore@py-v0.4.0...py-v0.5.0

v0.4.0

Compare Source

New Features 🪄
Breaking changes 🔧
  • get_range, get_range_async, get_ranges, and get_ranges_async now require named parameters for start, end, and length to make the semantics of the range request fully explicit. by @​kylebarron in #​156
  • Previously, individual stores did not manage a prefix path within the remote resource and PrefixStore was used to enable this. As of 0.4.0, PrefixStore was removed and all stores manage an optional mount prefix natively.
  • obstore.open has been renamed to obstore.open_reader.
  • The from_env constructor has been removed from S3Store, GCSStore, and AzureStore. Now all constructors will read from environment variables. Use __init__ or from_url instead. #​189
  • obstore.exceptions.ObstoreError renamed to obstore.exceptions.BaseError #​200
Bug fixes 🐛
Documentation 📖
Other
New Contributors

Full Changelog: developmentseed/obstore@py-v0.3.0...py-v0.4.0


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot enabled auto-merge (squash) November 9, 2025 14:10
@renovate
Copy link
Contributor Author

renovate bot commented Nov 9, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path bindings/python/Cargo.toml --package [email protected] --precise 0.5.0
error: failed to parse manifest at `/tmp/renovate/repos/github/codegen-sh/pink/bindings/python/Cargo.toml`

Caused by:
  error inheriting `edition` from workspace root manifest's `workspace.package.edition`

Caused by:
  failed to parse manifest at `/tmp/renovate/repos/github/codegen-sh/pink/Cargo.toml`

Caused by:
  the cargo feature `codegen-backend` requires a nightly version of Cargo, but this is the `stable` channel
  See https://doc.rust-lang.org/book/appendix-07-nightly-rust.html for more information about Rust release channels.
  See https://doc.rust-lang.org/cargo/reference/unstable.html#codegen-backend for more information about using this feature.

@renovate renovate bot force-pushed the renovate/pyo3-bytes-0.x branch from 4667a7e to 451f083 Compare November 20, 2025 21:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant