From 5d9f02d0e2ebb63404139297e949de3e1827ece7 Mon Sep 17 00:00:00 2001 From: Graham McIntire Date: Fri, 24 Apr 2026 08:54:40 -0500 Subject: [PATCH] chore(grid-rs): retrigger Rust CI to heal ImagePullBackOff The main-1776894678-93b526c image's index manifest references a platform-manifest digest (sha256:8850f92b...) that's no longer in the Forgejo registry. Both `latest` and the versioned tag point at the same broken digest, so every `docker pull` on talos5 has been 404ing for 14h. Bumping the crate root forces build-grid-rs.yaml's path filter to fire and push a fresh image. --- rust/prop_grid_rs/src/lib.rs | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/rust/prop_grid_rs/src/lib.rs b/rust/prop_grid_rs/src/lib.rs index 1cfac736..ec69d16c 100644 --- a/rust/prop_grid_rs/src/lib.rs +++ b/rust/prop_grid_rs/src/lib.rs @@ -1,5 +1,10 @@ //! Rust extraction of the Microwaveprop HRRR propagation pipeline. //! +//! CI retrigger 2026-04-24: Forgejo registry lost the platform-manifest +//! blob for tag main-1776894678-93b526c, leaving prop-grid-rs stuck in +//! ImagePullBackOff. Touching this file reruns build-grid-rs.yaml so a +//! fresh tag is pushed. +//! //! Each module mirrors the Elixir module it ports from so golden-fixture //! tests can compare behavior 1:1. Module boundaries chosen so failures //! during TDD fall into the smallest possible blast radius.