This site is being rebuilt and some pages are out of date. For current details, write to [email protected]. This notice goes away when the rebuild is done.

No analytics unless you allow it, no tracking. This site keeps in your browser the language you pick, the theme, its colour, which site you chose, the currency on the pricing page and that you closed this notice; signing in adds session cookies. The legal page has the details.

Sign in

Radar · Rust · Archive · Week 3 · Jan 12 – 18, 2026

diesel‑guard crate of the week

Nice to knowecosystem

What changed
The crate diesel‑guard is introduced as a linter against dangerous Postgres migrations.
Production impact
The source does not say.
Try it
Add diesel-guard to a Cargo.toml and run it against a migration file.
Source
this-week-in-rust.org/blog/2026/01/14/this-week-in-rust-634/

Understand it, then run it

Run it now

Todayrust
// This program demonstrates the problem that diesel-guard solves.
// It does not compile until the diesel-guard crate is available.
// The code below is a placeholder that would be linted by diesel-guard.

fn main() {
    // Imagine this is a migration that drops a column:
    // ALTER TABLE users DROP COLUMN age;
    println!("Migration would be flagged by diesel-guard as dangerous.");
}

What it printed when we ran it on Rust 1.98.1 (edition 2024)

Migration would be flagged by diesel-guard as dangerous.

Run sends this program (for Solidity, the contract and its tests) to our own sandbox, where it is compiled and run once, with no network, and what it printed or the test report comes back here. Nothing is kept. Runs are counted per visitor for the day so everyone gets a turn; the details are on the legal page.

Written by gpt-oss-20b from the linked source · claims checked against the sources · archive, not individually reviewed