feat: remove release.yml's cron — scheduling moves to the Brain nightly driver#129
Merged
Merged
Conversation
…ly driver Phase 2 of #127 (design §2): with a cron here, flipping RELEASE_MODE=live would have released ungated at 2 AM. Every run is now a workflow_dispatch (human or the nightly driver); resolve_mode drops the schedule branch and its RELEASE_MODE consult. Design note §4 updated to the implemented anchor: the NIGHTLY_LAST_WINDOW_END repo variable, advancing only on shipped / empty-skip outcomes. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Collaborator
Author
|
Phase-2 PR set for #127: PyAutoLabs/PyAutoBrain#63 (driver) · #129 (cron removal) · PyAutoLabs/PyAutoHeart#47 (release-ci profile) · PyAutoLabs/PyAutoMind#43 (digest watchdog). Merge Brain and Build the same day (Build-first leaves no scheduled path; Brain-first double-schedules nothing — the driver dispatches, the old cron rehearses — but same-day is tidiest); Heart and Mind are independent. |
This was referenced Jul 9, 2026
Merged
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
1 participant
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.
Phase 2 of #127 (design §2):
release.ymlloses itsschedule:trigger — scheduling authority moves to PyAutoBrain'snightly-release.yml(the activity-gated, Heart-GREEN-gated driver).This closes the standing hazard phase 1 flagged: with the cron here, flipping
RELEASE_MODE=livewould have performed a full live release at 2 AM gated on nothing but the TestPyPI build. After this PR every release run is aworkflow_dispatch(human or the nightly driver) andresolve_modeis just therehearsalinput passthrough — the schedule branch and itsRELEASE_MODEconsult are gone (the variable now governs nothing; retiring it is noted in the design as a later cleanup).Also updates
docs/nightly_release_design.md§4 to the implemented window anchor (theNIGHTLY_LAST_WINDOW_ENDrepo variable, advancing only on shipped/empty-skip outcomes) — the one phase-2 refinement over the phase-1 sketch, per the "update the note in the same PR" rule.Validation
YAML parses;
scheduleabsent;workflow_dispatchinputs and all 12 jobs unchanged apart from theresolve_modesimplification.API Changes
None — CI workflow + design doc only.
Scripts Changed
None.
Companion PRs: PyAutoBrain (the driver), PyAutoHeart (release-ci profile), PyAutoMind#43 (digest watchdog) — links in a comment. Merge note: from this merge until the Brain PR merges, no scheduled release path exists at all (manual dispatch unaffected) — merge the Brain PR the same day.
🤖 Generated with Claude Code