Skip to content

ci: trigger nightly path filter on any Cargo.toml change#5843

Merged
max-sixty merged 1 commit intoPRQL:mainfrom
max-sixty:nightly-cargo-paths
Apr 28, 2026
Merged

ci: trigger nightly path filter on any Cargo.toml change#5843
max-sixty merged 1 commit intoPRQL:mainfrom
max-sixty:nightly-cargo-paths

Conversation

@max-sixty
Copy link
Copy Markdown
Member

The nightly: path filter in tests.yaml had Cargo.toml (root-only) where it should have had **/Cargo.toml. PR #5834 only touched prqlc/prqlc/Cargo.toml, so test-deps-min-versions was skipped on its CI run, letting the chrono = "0.4" minimum-version regression land on main (now being fixed in #5841).

Audited the rest of the changes: block — every other filter that should match nested files already uses a ** glob. Cargo.lock (only one in the workspace), rust-toolchain.toml, and the bare Taskfile.yaml in the devcontainer filters (intentionally root-only) are unchanged.

This was written by Claude Code on behalf of @max-sixty

The bare `Cargo.toml` glob only matched the workspace root, so PR PRQL#5834
(which only touched `prqlc/prqlc/Cargo.toml`) skipped `test-deps-min-versions`
and the chrono = "0.4" minimum-version regression slipped through. Switch
to `**/Cargo.toml` so any workspace member's manifest sets `nightly = true`.

Co-Authored-By: Claude <noreply@anthropic.com>
@max-sixty max-sixty merged commit 01a307e into PRQL:main Apr 28, 2026
42 checks passed
@max-sixty max-sixty deleted the nightly-cargo-paths branch April 28, 2026 02:12
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