From 31071daf8646b2e1c9ba548f845d2ecc54091b18 Mon Sep 17 00:00:00 2001 From: Stefan Karpinski Date: Mon, 28 Sep 2026 20:58:22 +0000 Subject: [PATCH] Regenerate the stdlib map on a weekly schedule This workflow only ran when somebody dispatched it, so the map is correct about a new Julia release only if a person happens to act. Julia 1.13.1 was released on 2026-09-26, having bumped LLD_jll and libLLVM_jll to 20.1.8+2 and LibSSH2_jll to 1.11.104+0. The map had last been regenerated on 2026-09-08, so it was wrong about 1.13.1 from the moment that version existed, and would have stayed wrong for as long as nobody looked. It was fixed two days later because a downstream consumer pinning this package resolved 1.13.1 against 1.13.0's versions, noticed, and dispatched this workflow by hand. A Monday run bounds that: wrong for at most a week, and nobody has to think of it. The generator is unchanged, and create-pull-request updates the existing bot branch rather than opening a second one, so a week with no new Julia costs a no-op run. Two things this does not fix. The bot's pull requests still cannot start CI, since GITHUB_TOKEN-created ones never do, so each still wants a close/reopen to run check_hsg. And releasing is still manual -- the version bump and registration are not automated here -- so this shortens the gap between a Julia release and a pull request, not between a Julia release and a registered version. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_011hjZ6pHxaSNseY8pa5SKBx --- .github/workflows/run_hsg.yml | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/.github/workflows/run_hsg.yml b/.github/workflows/run_hsg.yml index 19c87f8..872a5df 100644 --- a/.github/workflows/run_hsg.yml +++ b/.github/workflows/run_hsg.yml @@ -1,6 +1,15 @@ name: Update Historical Stdlibs on: + # Julia releases a patch, its bundled stdlib versions move, and nothing here + # notices: this workflow only ever ran when somebody remembered to dispatch + # it. Julia 1.13.1 was released on 2026-09-26 and the map had last been + # regenerated on 2026-09-08, so the data was wrong about it immediately and + # would have stayed wrong indefinitely -- it was fixed two days later only + # because a downstream consumer hit the gap and dispatched this by hand. + # A weekly run turns "until somebody notices" into "by next Monday". + schedule: + - cron: '0 6 * * 1' workflow_dispatch: permissions: # Permissions for the `GITHUB_TOKEN` token