chore(deps): update cargo (minor/patch) - #310
Closed
renovate[bot] wants to merge 1 commit into
Closed
Conversation
renovate
Bot
force-pushed
the
renovate/cargo-(minorpatch)
branch
2 times, most recently
from
June 29, 2026 09:36
bf2d11a to
3cdc2ef
Compare
renovate
Bot
force-pushed
the
renovate/cargo-(minorpatch)
branch
from
June 29, 2026 09:55
3cdc2ef to
dc5ee06
Compare
Owner
|
Closing as blocked — not a fixable chore. object_store 0.13→0.14 cannot compile here: DataFusion 53 pins This will be lifted deliberately with a DataFusion upgrade (which also gates the thrift advisory #295). Renovate is constrained to hold object_store at <0.14.0 so it stops re-proposing this — see the linked config PR. |
jensholdgaard
added a commit
that referenced
this pull request
Jun 29, 2026
#313) DataFusion 53 pins object_store ^0.13, and ourios-querier registers ourios-parquet's Store::object_store() with DataFusion's SessionContext (register_object_store, querier/src/lib.rs), so the two crates must resolve to one object_store version. The renovate cargo (minor/patch) auto-merge kept proposing object_store 0.14 (#310), which splits the Arc<dyn ObjectStore> type at that boundary and breaks the build. Constrain object_store to <0.14.0 so it is lifted deliberately alongside a DataFusion upgrade (which also gates the thrift advisory, #295). Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
jensholdgaard
added a commit
that referenced
this pull request
Jul 2, 2026
…1, drafted) The #314 epic's RFC. Two phases, each following what upstream has shipped: - Phase 1 (now): DataFusion 53.1 → 54.0 unifies the workspace on one arrow (58.3; ourios-parquet moves off 55.2), removing the RFC 0017 dual decoder + view-types workaround (#276). MSRV 1.85 → 1.88 (DataFusion 54's floor). - Phase 2 (upstream-gated, expected ~DataFusion 55): object_store ≥ 0.14 (#310, renovate hold #313) + parquet 59 (drops thrift → #295); quick-xml deny-ignores removal iff object_store pins quick-xml ≥ 0.41. The boundary is upstream reality, not preference: DataFusion 54 pins object_store ^0.13.2 and parquet ^58.3 (thrift ^0.17 still present), so the epic's single coordinated bump is not constructible from released crates. Phase 1 deliberately isolates the riskiest part — arrow 55 → 58 on the on-disk-format pillar — with §3.3/§3.5 pinned as invariants (no schema bytes change; a committed pre-upgrade Parquet fixture makes "old files still read" a permanent regression test) and B1/B2 re-measured. §5 has 9 scenarios (.1–.6 phase 1; .7–.9 upstream-gated phase 2). Alternatives (single DF-55 bump, object_store fork, parquet-59-first) rejected in §4. Verified: mdbook build renders; SUMMARY.md entry added. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
jensholdgaard
added a commit
that referenced
this pull request
Jul 2, 2026
…21, drafted) (#337) * docs(rfc): phased DataFusion / Arrow upgrade behind upstream (RFC 0021, drafted) The #314 epic's RFC. Two phases, each following what upstream has shipped: - Phase 1 (now): DataFusion 53.1 → 54.0 unifies the workspace on one arrow (58.3; ourios-parquet moves off 55.2), removing the RFC 0017 dual decoder + view-types workaround (#276). MSRV 1.85 → 1.88 (DataFusion 54's floor). - Phase 2 (upstream-gated, expected ~DataFusion 55): object_store ≥ 0.14 (#310, renovate hold #313) + parquet 59 (drops thrift → #295); quick-xml deny-ignores removal iff object_store pins quick-xml ≥ 0.41. The boundary is upstream reality, not preference: DataFusion 54 pins object_store ^0.13.2 and parquet ^58.3 (thrift ^0.17 still present), so the epic's single coordinated bump is not constructible from released crates. Phase 1 deliberately isolates the riskiest part — arrow 55 → 58 on the on-disk-format pillar — with §3.3/§3.5 pinned as invariants (no schema bytes change; a committed pre-upgrade Parquet fixture makes "old files still read" a permanent regression test) and B1/B2 re-measured. §5 has 9 scenarios (.1–.6 phase 1; .7–.9 upstream-gated phase 2). Alternatives (single DF-55 bump, object_store fork, parquet-59-first) rejected in §4. Verified: mdbook build renders; SUMMARY.md entry added. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * docs(rfc): rfc 0021 status drafted → specified Maintainer ruling on Copilot's review finding: the RFC ladder places §5 acceptance-criteria authorship at the `specified` stage, so a document carrying a full §5/§6 carries `specified`, not `drafted` (matching the RFC 0020 precedent, which merged at `specified`). Status flipped; no content change. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
jensholdgaard
added a commit
that referenced
this pull request
Aug 29, 2026
NOT FOR MERGE AS-IS: the RFC0021.1 pin oracle fails on the version literals (see the PR body); rewriting it is an RFC 0021 phase-boundary amendment, which is a maintainer decision. What the spike establishes: - The whole workspace compiles and every non-container test passes except that one pin. Total API churn: one missed arrow-cast pin, and DataFusion 55's new required ExecutionPlan::apply_expressions, hit only by three test doubles in ourios-df-otel. - thrift is GONE from the lockfile (parquet 59 dropped it); cargo deny reports "no crate matched advisory criteria" for the GHSA ignore and passes clean — that is #295's clearance. - object_store stays 0.13.2: DataFusion 55 pins ^0.13.2, so #310 and the quick-xml ignores remain upstream-gated. Phase 2 is half-open. - MSRV 1.88 -> 1.94 (DataFusion 55's floor), which enables clippy's duration_suboptimal_units; it suggests Duration::from_days/from_mins, both UNSTABLE (rust#120301), so it is allowed workspace-wide with that reason rather than chased. Signed-off-by: Jens Holdgaard Pedersen <Jens@holdgaard.org>
jensholdgaard
added a commit
that referenced
this pull request
Aug 30, 2026
…e 2a) (#773) DataFusion 54→55, arrow/parquet 58→59, MSRV 1.88→1.94. thrift and paste leave the lockfile (#295 cleared; dead RUSTSEC-2024-0436 ignore removed). RFC0021.1 re-baselined to invariant + floors (arrow ≥59, DF ≥55, MSRV ≥1.94); RFC0021.8 thrift-absence test lands; §5/§5b split separates fired criteria from phase-2b forward declarations. The querier runs with execution.collect_statistics off via a shared exec::session() — DataFusion 55's constant-column substitution folds all-NULL columns to NULL literals and collapses body-equality predicates to constants, losing row-group pruning (pillar #1; caught by RFC0044.7/.8 + RFC0007.1). Upstream: apache/datafusion#24769, fix proposed in #24770. A unit test pins the override. Phase 2b (object_store ≥0.14: RFC0021.7 CAS re-proof, quick-xml ignores, renovate hold #313, #310) stays upstream-gated; epic #314. BREAKING CHANGE: workspace MSRV moves from 1.88 to 1.94; the storage/query stack moves to DataFusion 55 / arrow 59 / parquet 59. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Signed-off-by: Jens Holdgaard Pedersen <Jens@holdgaard.org>
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.
This PR contains the following updates:
=0.46.5→=0.46.60.13→0.141.23.3→1.23.4Release Notes
uuid-rs/uuid (uuid)
v1.23.4Compare Source
What's Changed
New Contributors
Full Changelog: uuid-rs/uuid@v1.23.3...v1.23.4
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.