ci(release): check for a nightly every three hours - #100
Merged
Conversation
61ba589 throttled the inherited three-hour nightly schedule to once a day because every rebuild was billable runner time. The repository is public and runs on GitHub-hosted standard runners now, so runner minutes cost nothing. Restore the three-hour cadence: check_changes still skips the run when pylon has not moved, so idle slots cost one short job, and active days rebuild at most eight times. docs/operations/release.md already documents the three-hour schedule, so the workflow and runbook agree again.
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What Changed
The nightly
scheduleinrelease.ymlgoes from0 9 * * *(daily) back to0 */3 * * *(every three hours), with the comment rewritten to say why. One line of YAML plus its comment.Why
61ba5899ethrottled the inherited three-hour cadence to once a day because "each rebuild is billable" on Blacksmith. After #99 the repository is public and every job runs on GitHub-hosted standard runners, where minutes are free, so that reason is gone.What keeps this from costing more:
check_changesstill runs first and skips the whole release whenpylonhas not moved since the last nightly tag, so an idle three-hour slot is one ~20 s Linux job.vX.Y.Z-nightly.YYYYMMDD.<run>), so several builds on one day cannot collide.release-nightlyconcurrency group withcancel-in-progressmeans a new scheduled run supersedes a stale in-flight one rather than stacking.pylon-releasesasset feed; at a maximum of eight builds on an active day both stay far inside their limits.docs/operations/release.mdalready documents "scheduled check every three hours" in two places — it was never updated for the daily throttle — so this change brings the workflow back in line with the runbook rather than requiring a doc edit.Checklist
Model: Claude Fable 5 · Harness: Claude Code
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.