Skip to content

ci: add a CI job that builds without the lockfile #20758

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
westonpace wants to merge 2 commits into
base: main
Choose a base branch
from
+20 −0
Open

ci: add a CI job that builds without the lockfile #20758

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
51f1eac
Add a CI job that builds without the lockfile
westonpace Mar 6, 2026
ad163e7
Revert unintentional lockfile changes
westonpace Mar 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions .github/workflows/rust.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -69,11 +69,31 @@
# the changes to `Cargo.lock` after building with the updated manifest.
cargo check --profile ci --workspace --all-targets --features integration-tests --locked

# Check the workspace compiles without a lock file
#
# This catches downstream breaking changes from dependencies
# as soon as possible by resolving deps fresh (without Cargo.lock).
linux-build-no-lock:
name: cargo check (no lock)
runs-on: ubuntu-latest
container:
image: amd64/rust
steps:
- uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
- name: Setup Rust toolchain
uses: ./.github/actions/setup-builder
with:
rust-version: stable
- name: Remove Cargo.lock
run: rm Cargo.lock
- name: Check workspace
run: cargo check --profile ci --workspace --all-targets --features serde,avro,json,backtrace,integration-tests,parquet_encryption

# Check datafusion-common features
#
# Ensure via `cargo check` that the crate can be built with a
# subset of the features packages enabled.
linux-datafusion-common-features:

Check warning

Code scanning / CodeQL

Workflow does not contain permissions Medium

Actions job or workflow does not limit the permissions of the GITHUB_TOKEN. Consider setting an explicit permissions block, using the following as a minimal starting point: {contents: read}
name: cargo check datafusion-common features
needs: linux-build-lib
runs-on: ubuntu-latest
Expand Down
Loading