Skip to content

Check in Cargo.lock - #2482

Open
alamb wants to merge 2 commits into
apache:mainfrom
alamb:checkin-cargo-lock
Open

Check in Cargo.lock#2482
alamb wants to merge 2 commits into
apache:mainfrom
alamb:checkin-cargo-lock

Conversation

@alamb

@alamb alamb commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

Which issue does this PR close?

N/A

Rationale for this change

Checking in Cargo.lock gives CI reproducible builds and makes dependency updates visible in review, per the current Cargo guidance which now recommends committing the lockfile for libraries as well.

What changes are included in this PR?

  • Remove Cargo.lock from .gitignore
  • Check in Cargo.lock generated with cargo update (all 46 packages locked to the latest semver-compatible versions; no Cargo.toml changes needed)

Are these changes tested?

cargo test --all-features passes (22/22 suites, 0 failures).

Are there any user-facing changes?

No. This only affects local development and CI of this repository; downstream users of the published crate are unaffected.

@alamb alamb changed the title Check in Cargo.lock, update dependencies to latest compatible versions Check in Cargo.lock Sep 7, 2026
@alamb
alamb marked this pull request as ready for review September 7, 2026 10:45

@LucaCappelletti94 LucaCappelletti94 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To make dependency updates reliably visible in review, maybe we should use --locked in the CI? The sqlparser_bench job uses an independent manifest, so it likely needs its own committed lockfile, or possibly better a workspace integration.

Comment thread Cargo.lock
@@ -0,0 +1,412 @@
# This file is automatically @generated by Cargo.
# It is not intended for manual editing.
version = 4

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At this time https://github.com/apache/datafusion-sqlparser-rs/blob/main/.tool-versions still specifies Rust 1.75, and version = 4 is only supported from 1.78. I suspect that the current CI misses this because it tests only stable, beta, and nightly, and not specifically 1.75.

I am not sure whether here we would want to either bump .tool-versions or downgrade the version of the Cargo.lock.

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.

2 participants