fix(sqlite): avoid deprecated time format components - #62
Merged
Merged
Conversation
This was referenced Sep 27, 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.
The committed time 0.3.55 dependency deprecates the manually constructed date/time components and byte literals, causing 40 errors under CI's
-D warningseven with Rust pinned to 1.98.1. This is the failure blocking #61.Build the existing SQLite format descriptions with time's compile-time macro, retaining the same optional separators, seconds, fractions and offsets. This avoids a dependency bump or warning suppression.
Validation on Rust 1.98.1:
cargo fmt --all -- --check-D warnings, for both native-tls and rustls.Local test/build commands used
--locked; commands involving vendored OpenSSL usedOPENSSL_NO_VENDOR=1to use the installed system OpenSSL.