Compliance reports lost the version switcher + back-link (0.15.0 vs 0.1.0): release/compliance.yml don't pass homepage/other-versions

[avrabe]

Reported by the maintainer: the published compliance report for 0.15.0 (pulseengine.eu/reports/rivet/0.15.0/compliance/) has no version selector and no "way back" navigation, both of which 0.1.0 has.

Diagnosis (traced through this repo)

The report generator is intact — nothing was removed:

• rivet export --format html still supports --homepage <url> (the "← back" link), --versions '[{label,path},…]' (the version-switcher dropdown), and --version-label (rivet-cli/src/main.rs:603–634). These are written into the report's config.js, which the page reads at runtime.
• The compliance action exposes them as homepage / other-versions / report-label inputs (.github/actions/compliance/action.yml:199–214), adding the flags only when non-empty.

The regression is that the inputs aren't supplied:

1. release.yml build-compliance passes none of them (only theme / single-page / include-data-formats), and merely uploads the report as a GitHub artifact — it doesn't publish to pulseengine.eu/reports/.
2. The reusable compliance.yml workflow doesn't even expose other-versions or report-label (only version/homepage/theme/offline) — so any caller using it cannot produce a switcher.
3. The actual publishing to reports/rivet/<ver>/ happens in a separate pulseengine.eu site pipeline (not in this repo). That's the only layer that knows the full version list, so the cross-version switcher must be populated there. The 0.1.0→0.15.0 regression is in that pipeline (it stopped passing --homepage/--versions or writing them into config.js).

Also found

pulseengine.eu's TLS certificate is expired — the report URLs don't load at all (certificate has expired). Worth renewing.

Fix

• Root cause (site repo, not here): when publishing each report, pass --homepage https://pulseengine.eu/… and --versions '[…all versions…]', then re-run over 0.15.0 (+ back-fill).
• In this repo (ergonomic gaps that make the trap easy) — REQ-163, PR incoming:
  • add other-versions + report-label passthrough inputs to the reusable compliance.yml so a caller can get a switcher;
  • give release.yml's compliance step a default homepage so even the GH-artifact report has a back-link.

Found while answering the maintainer's question during the dogfooding loop.

[avrabe]

The in-repo half of this is now merged (#421 / REQ-163): compliance.yml maps version → report-label and forwards a new other-versions passthrough; release.yml labels the report with the release tag and sets a default homepage. So a caller can now produce both the back-link and the version switcher.

Still open (the live regression): the published reports at pulseengine.eu/reports/rivet/<ver>/ are assembled by the site-publishing pipeline (not this repo), which is the only layer that knows the full version list for the switcher. Re-publishing 0.15.0 (and back-filling) must pass --versions '[…all versions…]' + --homepage there. Also still flagged: the site's expired TLS cert (the report URLs don't load).

Leaving this issue open for the site-side fix; the rivet-side enablement is done.

[avrabe]

Triaged from the dogfooding loop — the in-repo half is already done; what remains is outside this repo.

✅ In-rivet-repo ergonomic fixes: shipped (REQ-163, status implemented). Verified on main:

• .github/workflows/compliance.yml now exposes other-versions + report-label and forwards them to the report action (lines 21, 62–66), so a caller can produce the version switcher.
• .github/workflows/release.yml build-compliance now passes a default homepage (line 178) so even the GH-artifact report has a back-link.

So there is no remaining actionable work in this repo for the switcher itself.

❌ Remaining (both outside pulseengine/rivet):

1. The pulseengine.eu site pipeline must pass --versions '[…all versions…]' (the full cross-version list) when (re)publishing each reports/rivet/<ver>/ — that pipeline is the only layer that knows every version. Back-fill 0.15.0. (Different repo.)
2. The TLS cert is still expired — verified just now: notAfter = May 31 12:09:32 2026 GMT, and curl https://pulseengine.eu/ → certificate has expired. It's been down ~6 days, so the report URLs don't load at all regardless of the switcher. Renewing the cert is the most urgent item here (the published compliance evidence is currently inaccessible).

Recommend closing the rivet-repo scope of this issue (REQ-163 covers it) and tracking the site-pipeline + cert items wherever the pulseengine.eu site is managed.