Will Jones a12b28cae6 chore(deps): only update Cargo.lock, not Cargo.toml requirements ...

Dependabot raised the lower-bound version requirements in Cargo.toml
(arrow, tokio, aws-sdk-*, etc.) to match the new lockfile versions. That
forces our library's consumers onto newer minimum versions and broke the
MSRV check, which downgrades aws-sdk-* crates to verify they still build
on Rust 1.91 — the downgrades could no longer satisfy the bumped
constraints.

Revert all Cargo.toml changes and regenerate Cargo.lock within the
existing requirement ranges. The point of this dependabot job is to keep
the lockfile (and the binaries we ship) current on security fixes, not
to bump our public minimum versions.

Also set `versioning-strategy: lockfile-only` so future dependabot PRs
only touch Cargo.lock.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-14 15:51:15 -07:00

..

actions/create-failure-issue

ci: automatic issue creation for failed publish workflows (#2694)

2025-10-02 08:24:16 -07:00

ISSUE_TEMPLATE

docs: fix broken documentation links (#3278)

2026-04-15 20:56:59 +08:00

workflows

ci(nodejs): switch from npm to pnpm 11 (#3373)

2026-05-13 11:27:38 -07:00

dependabot.yml

chore(deps): only update Cargo.lock, not Cargo.toml requirements

2026-05-14 15:51:15 -07:00

labeler.yml

ci: write down breaking change policy (#1294)

2024-05-13 10:25:55 -07:00

release_notes.json

ci: make preview releases (#1302)

2024-05-17 11:24:38 -07:00