From 2fc764c1e8e664fe65411645bf4869c6c5aeb940 Mon Sep 17 00:00:00 2001 From: Ruben Hensen Date: Thu, 30 Jul 2026 20:44:21 +0200 Subject: [PATCH] ci: unignore the tracked JWT rotation fixtures so release-plz runs Root .gitignore's `*.pem` matches the four fixtures #241 committed under pg-pkg/testdata/jwt_rotation/, leaving them tracked *and* ignored. release-plz refuses to run against a repo in that state, so delivery.yml's `Release-plz PR` job has failed on every push to main since #241 landed on 2026-07-16, twelve runs. `Release-plz release` is a separate job and was unaffected, which is why releases kept working and nothing looked broken. The visible damage is PR #187 (`chore: release`), still open and last updated 2026-07-16, so it is missing the version bumps and changelog entries for everything merged after that date. The negation is scoped to that one directory, so no other .pem is unignored. The fixtures are throwaway RSA keypairs for a single regression test and are already in history; this changes how git treats them, not what is committed. Closes #273 --- .gitignore | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/.gitignore b/.gitignore index 2c171b2c..e96ec779 100644 --- a/.gitignore +++ b/.gitignore @@ -18,3 +18,11 @@ pkg_ibs.sec # `--manifest-path pg-wasm/Cargo.toml` resolves it on its own and writes a # lockfile next to the manifest. The repo does not track it. pg-wasm/Cargo.lock + +# #241's JWT-rotation fixtures are committed, and `*.pem` above would otherwise +# leave them tracked *and* ignored. release-plz refuses to run against a repo in +# that state, which took delivery.yml's `Release-plz PR` job down (#273); the +# `Release-plz release` job is separate and kept working, so nothing looked +# broken. `git ls-files -ci --exclude-standard` lists what is in that state, and +# must stay empty. +!pg-pkg/testdata/jwt_rotation/*.pem