From a7bc3ae3ec3913d565d739b046d6ecd7820dfce8 Mon Sep 17 00:00:00 2001 From: Ruben van der Linde Date: Mon, 24 Aug 2026 11:11:08 +0200 Subject: [PATCH 1/2] fix(docs): publish from development, to the worker that actually serves this site MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Two silent failures, both of which had to be fixed before this site could update at all. 1. The workflow triggered on `documentation`, a branch that exists but nobody updates. Green and idle for months while the live site aged. 2. `worker-name` was never passed, so the callee derived it from `cname`. Since the app-id rename `cname` is the NEW host, while the worker that actually holds the custom domains is still named after the OLD app id. The derived name points at a worker that does not exist — deploying it CREATES a second worker while both custom domains keep routing to the original. Every deploy green, reaching nobody, with the live-site verification added in ConductionNL/.github#555 as the only thing that would ever have noticed. Measured today: both hostnames still serve the pre-rename title while docs/docusaurus.config.js has carried the new one since the rename. Nothing has carried a build to the edge. --- .github/workflows/documentation.yml | 34 +++++++++++++++++++---------- 1 file changed, 23 insertions(+), 11 deletions(-) diff --git a/.github/workflows/documentation.yml b/.github/workflows/documentation.yml index fb58a0bb..11074a48 100644 --- a/.github/workflows/documentation.yml +++ b/.github/workflows/documentation.yml @@ -1,10 +1,16 @@ name: Documentation on: + # `development` is where the work lands. This used to trigger on a + # `documentation` branch that exists but nobody updates — so the workflow + # was green and idle while the live site aged. Measured today: + # softwarecatalog.conduction.nl and stackiq.conduction.nl both still serve + # the pre-rename "SoftwareCatalog" title while docs/docusaurus.config.js + # says 'Stackiq'. push: - branches: [documentation] + branches: [development] pull_request: - branches: [documentation] + branches: [development] jobs: deploy: @@ -17,7 +23,7 @@ jobs: # # ⚠️ `packages: write` is load-bearing at RUNTIME, not merely statically: # the callee's `build-image` input DEFAULTS TO TRUE, so the `image` job - # really does run on a push to `documentation` and really does push to + # really does run on a push to `development` and really does push to # GHCR. Dropping it 403s that push. # # It would be required even if that job were disabled, because GitHub @@ -29,13 +35,19 @@ jobs: packages: write uses: ConductionNL/.github/.github/workflows/documentation.yml@main with: - # FROZEN through the stackiq -> stackiq app-id rename. - # `stackiq.conduction.nl` answers 200 today; `stackiq.conduction.nl` - # answers 000 (no DNS record). A CNAME is not a name we own in this repo — - # it is a claim about a record that exists. Publishing docs at a host that - # resolves to nothing takes the documentation site OFFLINE, which is a - # regression, not a rename. Move this only after DNS + the Pages/Cloudflare - # binding for the new host are live, in a change that verifies both. + # `stackiq.conduction.nl` resolves as of 2026-08-23 — attached as a + # second custom domain on the SAME `softwarecatalog-docs` worker that + # serves `softwarecatalog.conduction.nl`. Both hosts answer 200. + # (The comment that used to sit here said the new host answered 000; + # that was true when it was written and is not any more.) cname: stackiq.conduction.nl - docs-hosts: softwarecatalog.conduction.nl,stackiq.conduction.nl \ No newline at end of file + docs-hosts: softwarecatalog.conduction.nl,stackiq.conduction.nl + + # The worker that ALREADY holds both custom domains. Without this the + # callee derives the name from `cname` — `stackiq-docs` — which does not + # exist. Deploying that would create a SECOND worker while both custom + # domains keep routing to `softwarecatalog-docs`: every deploy green, + # reaching nobody. Renaming the worker is a Cloudflare-side move, not + # something this file can perform. + worker-name: softwarecatalog-docs From f83d13efea65f727c1f5bfa025142fbfae33e866 Mon Sep 17 00:00:00 2001 From: Ruben van der Linde Date: Mon, 24 Aug 2026 11:40:17 +0200 Subject: [PATCH 2/2] fix(docs): ship the og:image file the config already names MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The docs build FAILS, and has been failing — it was simply never run, because the workflow triggered on a branch nobody updates. Making the trigger correct surfaced it on the first run. The app-id rename updated `docusaurus.config.js` to point og:image at the new filename and left the actual PNG under its old name, so the AI-baseline validator's last check fails: ✗ og:image URL resolves to a file in the build and `npm run build` exits 1 via postbuild. Nothing could have published even with a correct trigger and a correct worker. Renames the asset to the name the config has been asking for. No references to the old filename remain. Verified locally: npm ci --legacy-peer-deps && npm run build now exits 0 with all 10 AI-baseline checks passing. --- .../img/{og-softwarecatalog.png => og-stackiq.png} | Bin 1 file changed, 0 insertions(+), 0 deletions(-) rename docs/static/img/{og-softwarecatalog.png => og-stackiq.png} (100%) diff --git a/docs/static/img/og-softwarecatalog.png b/docs/static/img/og-stackiq.png similarity index 100% rename from docs/static/img/og-softwarecatalog.png rename to docs/static/img/og-stackiq.png