Skip to content

fix(sqlite): silence time 0.3.48 modifier deprecations under -D warnings#4311

Open
ricochet wants to merge 1 commit into
transact-rs:mainfrom
ricochet:fix/sqlite-time-modifier-deprecations
Open

fix(sqlite): silence time 0.3.48 modifier deprecations under -D warnings#4311
ricochet wants to merge 1 commit into
transact-rs:mainfrom
ricochet:fix/sqlite-time-modifier-deprecations

Conversation

@ricochet

@ricochet ricochet commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

This change adds #![allow(deprecated)] for sqlite time formats to silence clippy warnings.

time 0.3.48 deprecated the field-based modifier::{Year, Month, Hour} format components and raw-byte Literal, which broke clippy -D warnings in CI (no Cargo.lock, so the latest time is resolved). The new #[non_exhaustive] replacements aren't const-constructible the way these const format items need, and the deprecated API still works, so scope an to mod formats as a stopgap.

Does your PR solve an issue?

This is a stopgap for #4310. #4310 tracks performing a migration, while this change gets main CI back to passing.

Is this a breaking change?

No. To fully complete #4310, possibly but this PR does not cover that.

time 0.3.48 deprecated the field-based `modifier::{Year, Month, Hour}`
format components and raw-byte `Literal`, which broke `clippy -D warnings`
in CI (no Cargo.lock, so the latest `time` is resolved). The new
`#[non_exhaustive]` replacements aren't const-constructible the way these
`const` format items need, and the deprecated API still works, so scope an
`#![allow(deprecated)]` to `mod formats` as a stopgap.

Tracking for migration: transact-rs#4310

Signed-off-by: Bailey Hayes <bailey@cosmonic.com>
@ricochet

Copy link
Copy Markdown
Contributor Author

Going to close/re-open this pr to re-trigger workflow. Hit flake in https://github.com/transact-rs/sqlx/actions/runs/27626477394/job/81690173856?pr=4311:

 Network sqlx_default  Creating
 Network sqlx_default  Created
 mysql_8 Pulling 
 mysql_8 Error Get "https://registry-1.docker.io/v2/": context deadline exceeded
Error response from daemon: Get "https://registry-1.docker.io/v2/": context deadline exceeded

@ricochet ricochet closed this Jun 16, 2026
@ricochet ricochet reopened this Jun 16, 2026
@lf-

lf- commented Jun 19, 2026

Copy link
Copy Markdown

FYI, careful with your PR message as you'll accidentally close #4310.

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