Repository navigation
fix(deps): pin SQLQuack 0.5.0 - #63
Merged
Merged
Conversation
SQLQuack 0.5.0 (c0327785) is its first tagged release after 2096c698. SQLBuild needs its set-operation lineage fix and can only take it with a single SQLQuack copy if SQLClean pins the same revision. Formatting, query fingerprints and lint do not change: a dump of all three over 11,573 queries in every dialect is byte-identical to the one on 2096c698.
Deploying sqlclean with
|
| Latest commit: |
2719419
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://c5746d6a.sqlclean.pages.dev |
| Branch Preview URL: | https://fix-pin-sqlquack-050.sqlclean.pages.dev |
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.
Why
SQLQuack 0.5.0 (
c0327785, tag v0.5.0) is SQLQuack's first tagged release after2096c698. SQLBuild needs its set-operation lineage fix. It links SQLClean and SQLQuack into one binary, so SQLClean has to pin the same revision for the build to keep a single SQLQuack copy.Changes
Cargo.tomlandCargo.lock: all six directsqlquack-*pins (11 locked packages) move from2096c698toc0327785f79c0f8c2c0abd44b06b2de2f2b3659a.Verification
query_fingerprintand lint with every catalogue rule. The 81,011 records are byte-identical to2096c698's (cmp), sha256310eb2b9…for both.cargo fmt --checkandcargo clippy --all-targets -- -D warningsare clean.cargo test --workspace --locked: 48 passed.