Skip to content

deps: arrow/parquet 59.3.0 and six minor bumps, with the SBOM regenerated - #82

Merged
RobbinBouwmeester merged 2 commits into
mainfrom
deps/lockfile-bumps
Sep 12, 2026
Merged

deps: arrow/parquet 59.3.0 and six minor bumps, with the SBOM regenerated#82
RobbinBouwmeester merged 2 commits into
mainfrom
deps/lockfile-bumps

Conversation

@RobbinBouwmeester

Copy link
Copy Markdown
Member

Supersedes #49 (arrow-parquet group) and #51 (rust-minor-and-patch group).

Why those two have been red for a week

Not a conflict — both still report MERGEABLE. sbom.cdx.json and THIRD_PARTY_LICENSES.md are tracked and pin exact dependency versions, and CI runs gen_sbom.py --check and gen_third_party_licenses.py --check in the "python sidecars + configs" job. Any lock bump fails that job until both are regenerated, and regenerating them is a step Dependabot does not take. So those PRs could never go green on their own.

What is in this one

Lock only. No manifest constraint changed, so every bump is semver-compatible with what Cargo.toml already asks for:

crate from to
arrow, parquet (+15 arrow-*) 59.0.0 59.3.0
anyhow 1.0.103 1.0.104
blake3 1.8.5 1.8.7
clap 4.6.1 4.6.6
serde_json 1.0.150 1.0.151
thiserror 2.0.18 2.0.20
base64 (transitive) 0.22.1 0.23.1

serde stays at 1.0.228. Dependabot proposed 1.0.229; it does not resolve under the current graph, so it is not applied here.

mzdata is deliberately not in this PR. #52 moves it 0.65.5 → 0.66.6, which is a breaking change for a 0.x crate, a manifest edit, and in the library that parses mzML. It gets its own PR with a conversion-output comparison.

Validation

cargo fmt --check, clippy --all-targets --locked -D warnings, cargo test --workspace --locked (284), cargo audit clean, and both generators --check clean after regeneration. SBOM 175 → 174 components (arrayref dropped by the blake3 update).

Suggested follow-up

This will recur on every Dependabot run. Worth deciding whether CI should regenerate these two files rather than only check them, or whether Dependabot should be pointed at a job that does. Happy to implement whichever you prefer.

🤖 Generated with Claude Code

Supersedes the Dependabot PRs #49 (arrow-parquet group) and #51
(rust-minor-and-patch group), which have been red for a week for a reason
Dependabot cannot fix: `sbom.cdx.json` and `THIRD_PARTY_LICENSES.md` are tracked
and pin exact dependency versions, and CI runs `gen_sbom.py --check` and
`gen_third_party_licenses.py --check`. Any lock bump therefore fails that job
until both are regenerated, which is a step Dependabot does not take. Landing the
bumps by hand with the regeneration included is what actually goes green.

Lock only; no manifest constraint changed, so every one of these is
semver-compatible with what `Cargo.toml` already asks for:

  arrow, parquet   59.0.0  -> 59.3.0  (and the fifteen arrow-* crates)
  anyhow           1.0.103 -> 1.0.104
  blake3           1.8.5   -> 1.8.7
  clap             4.6.1   -> 4.6.6
  serde_json       1.0.150 -> 1.0.151
  thiserror        2.0.18  -> 2.0.20
  base64           0.22.1  -> 0.23.1  (transitive, pulled by the arrow update)

serde stayed at 1.0.228: 1.0.229 does not resolve under the current graph, so
Dependabot's proposed bump for it is not applied here.

mzdata is deliberately untouched. #52 moves it 0.65.5 -> 0.66.6, which is a
BREAKING change for a 0.x crate and a manifest edit, in the library that parses
mzML. It gets its own branch and a conversion-output comparison rather than
riding along with a lock refresh.

Validated: `cargo fmt --check`, `clippy --all-targets --locked -D warnings`,
`cargo test --workspace --locked` (284), `cargo audit` clean, and both generators
`--check` clean after regeneration. The SBOM goes from 175 to 174 components
(arrayref dropped by the blake3 update).

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
# Conflicts:
#	THIRD_PARTY_LICENSES.md
#	sbom.cdx.json
@RobbinBouwmeester
RobbinBouwmeester merged commit ea4fafa into main Sep 12, 2026
12 checks passed
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