ci: lock PR dependencies and check upstream compatibility weekly - #64
Merged
Merged
Conversation
lovasoa
force-pushed
the
codex/lock-ci-dependencies
branch
from
September 27, 2026 23:11
e0afd35 to
5afc733
Compare
lovasoa
enabled auto-merge
September 27, 2026 23:11
github-merge-queue
Bot
removed this pull request from the merge queue due to no response for status checks
Sep 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Use
--lockedfor all 24 build, test and Clippy commands in PR/main CI so dependency resolution cannot silently change the committed baseline. Document that dependency changes must include their lockfile updates.Add a separate weekly/manual Upstream compatibility workflow that runs
cargo updateand exercises Clippy, core unit tests and SQLite type tests on latest stable for both TLS backends. Its explicitRUSTUP_TOOLCHAIN=stableoverrides the shared toolchain pin proposed in #63. It has read-only repository permissions, never commits the generated lockfile and does not run on pull requests.Validation:
bash -n.--lockedand compatibility runs only on schedule/manual dispatch.cargo metadata --locked --offline --no-deps --format-version 1passed.--lockedwhile validating fix(sqlite): avoid deprecated time format components聽#62.Independent PR based on main. Merge #62 first to resolve the existing time deprecation errors; this PR does not change dependency versions. The scheduled workflow's fresh dependency resolution and full test run will be validated when it runs.