From 2682b15f41a6d3fed7f22cd03e97be8d0419b712 Mon Sep 17 00:00:00 2001
From: Urgau <urgau@numericable.fr>
Date: Sat, 4 May 2024 16:02:46 +0200
Subject: [PATCH] Change the schedule to tomorrow (2024-05-05)

---
 posts/{2024-05-08-check-cfg.md => 2024-05-05-check-cfg.md}  | 6 +++---
 .../cargo-check.svg                                         | 0
 2 files changed, 3 insertions(+), 3 deletions(-)
 rename posts/{2024-05-08-check-cfg.md => 2024-05-05-check-cfg.md} (96%)
 rename static/images/{2024-05-08-check-cfg => 2024-05-05-check-cfg}/cargo-check.svg (100%)

diff --git a/posts/2024-05-08-check-cfg.md b/posts/2024-05-05-check-cfg.md
similarity index 96%
rename from posts/2024-05-08-check-cfg.md
rename to posts/2024-05-05-check-cfg.md
index 2d13498c0..3944e6368 100644
--- a/posts/2024-05-08-check-cfg.md
+++ b/posts/2024-05-05-check-cfg.md
@@ -7,7 +7,7 @@ team: The Cargo Team <https://www.rust-lang.org/governance/teams/dev-tools#cargo
 
 # Automatic checking of cfgs at compile-time
 
-The Cargo and Compiler team are delighted to announce that starting with Rust 1.80 (or nightly-2024-05-08) every _reachable_ `#[cfg]` will be automatically checked that they match the expected config names and values.
+The Cargo and Compiler team are delighted to announce that starting with Rust 1.80 (or nightly-2024-05-05) every _reachable_ `#[cfg]` will be automatically checked that they match the expected config names and values.
 
 This can help with verifying that the crate is correctly handling conditional compilation for different target platforms or features. It ensures that the cfg settings are consistent between what is intended and what is used, helping to catch potential bugs or errors early in the development process.
 
@@ -48,7 +48,7 @@ fn win() {}
 ```
 
 *`cargo check`*:
-![cargo-check](../../../../images/2024-05-08-check-cfg/cargo-check.svg)
+![cargo-check](../../../../images/2024-05-05-check-cfg/cargo-check.svg)
 
 ## Custom cfgs and build scripts
 
@@ -56,7 +56,7 @@ fn win() {}
 
 Some crates use custom cfgs that they either expected from the environment (`RUSTFLAGS`or other means) or is enabled by some logic in the crate `build.rs`. For those crates Cargo provides a new instruction: [`cargo::rustc-check-cfg`](https://doc.rust-lang.org/nightly/cargo/reference/build-scripts.html#rustc-check-cfg)[^2] (or `cargo:rustc-check-cfg` for older Cargo version).
 
-[^2]: `cargo::rustc-check-cfg` will start working in Rust 1.80 (or nightly-2024-05-08). From Rust 1.77 to Rust 1.79 *(inclusive)* it is silently ignored. In Rust 1.76 and below a warning is emitted when used without the unstable Cargo flag `-Zcheck-cfg`.
+[^2]: `cargo::rustc-check-cfg` will start working in Rust 1.80 (or nightly-2024-05-05). From Rust 1.77 to Rust 1.79 *(inclusive)* it is silently ignored. In Rust 1.76 and below a warning is emitted when used without the unstable Cargo flag `-Zcheck-cfg`.
 
 The syntax to use is described in the [rustc book](https://doc.rust-lang.org/nightly/rustc/) section [checking configuration](https://doc.rust-lang.org/nightly/rustc/check-cfg.html), but in a nutshell the basic syntax of `--check-cfg` is:
 
diff --git a/static/images/2024-05-08-check-cfg/cargo-check.svg b/static/images/2024-05-05-check-cfg/cargo-check.svg
similarity index 100%
rename from static/images/2024-05-08-check-cfg/cargo-check.svg
rename to static/images/2024-05-05-check-cfg/cargo-check.svg