Skip to content

governance(auto-release): drop update-website-badge job#574

Merged
ChBrain merged 1 commit into
mainfrom
governance/drop-website-badge-job
May 27, 2026
Merged

governance(auto-release): drop update-website-badge job#574
ChBrain merged 1 commit into
mainfrom
governance/drop-website-badge-job

Conversation

@ChBrain

@ChBrain ChBrain commented May 27, 2026

Copy link
Copy Markdown
Owner

Phase B. The update-website-badge job in auto-release.yml is dead code — KAIHACKS PR #273 (merged) put the version badge on a self-updating path: cultures-map.js reads data.release from available.json on page load and writes both the href and the visible text dynamically.

Why this is now dead code

The job tries to sed-replace two patterns in kaihacks.ai/cultures/public_html/map/index.html:

href="https://github\.com/ChBrain/Cultures/releases/tag/v[\d\.]+"
>v[\d\.]+ &nearr;<

But the actual badge line on KAIHACKS main (post-#273) reads:

<a href="https://github.com/ChBrain/Cultures/releases" class="worldmap__version" ...>download &nearr;</a>
  • The href has no /tag/vX.Y.Z suffix
  • The visible text has no vX.Y.Z prefix

So on every Cultures release the job runs, both regexes match nothing, the file is unchanged, and the workflow either errors on git commit (no changes) or opens an empty PR against KAIHACKS. That noise stops once this PR lands.

Result

After this change, a Cultures release opens exactly one PR against KAIHACKS — the deliver-available-json job's PR carrying available.json (and groupings.json once that pipeline is live in production). The badge updates client-side from that same available.json on the next page load — no PR needed.

Remaining jobs unchanged

Job Purpose
release Cuts the release on main
deliver-available-json Opens the KAIHACKS PR with manifests
build-zips Publishes culture/engine/groups zips to the release
build-pdfs Publishes PDFs to the release

Diff

-65 lines (entire update-website-badge job + its leading comment block).

Verification

Check Result
python -c "import yaml; yaml.safe_load(open('.github/workflows/auto-release.yml'))" parses ✅
Jobs remaining release, deliver-available-json, build-zips, build-pdfs (4/4 expected) ✅
python tests/branch_scope.py advise governance/<name> (base main) ✅

Ref: ChBrain/KAIHACKS#273, ChBrain/KAIHACKS#268 (superseded)


Generated by Claude Code

The job is dead code. KAIHACKS PR #273 (merged) put the version badge
on a self-updating path: cultures-map.js reads data.release from
available.json on page load and writes both the href and the visible
text dynamically. The hardcoded vX.Y.Z patterns the job tried to
sed-replace in map/index.html no longer exist there:

  href="https://github.com/ChBrain/Cultures/releases"      (no /tag/v...)
  >download &nearr;<                                       (no vX.Y.Z prefix)

So on every Cultures release the job currently runs both regex
substitutions, matches nothing, has no file changes to commit, and
either errors on git commit or opens an empty PR against KAIHACKS.
That noise stops once this PR lands.

After this change, a Cultures release opens exactly ONE PR against
KAIHACKS -- the deliver-available-json job's PR carrying
available.json (and groupings.json once that pipeline is live).
The badge updates client-side from that same available.json on the
next page load, no PR needed.

Files:
- .github/workflows/auto-release.yml: -65 lines (entire
  update-website-badge job and its leading comment).

Remaining jobs in this workflow are unchanged:
- release (cuts the release on main)
- deliver-available-json (opens the KAIHACKS PR with manifests)
- build-zips (publishes culture/engine/groups zips to the release)
- build-pdfs (publishes PDFs to the release)

Ref: ChBrain/KAIHACKS#273, ChBrain/KAIHACKS#268 (superseded)
@ChBrain
ChBrain merged commit 5d273e3 into main May 27, 2026
53 checks passed
@ChBrain
ChBrain deleted the governance/drop-website-badge-job branch May 27, 2026 08:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants