Context
.github/dependabot.yml schedules both ecosystems (npm, github-actions) with interval: daily, which Dependabot runs Monday to Friday only. The dynamic npm_and_yarn in /. job ran at 07:31Z on Oct 28–30 and Nov 2–6, with no runs on Oct 31, Nov 1, Nov 7 or Nov 8. neo-agent-skills ships one or more versions a day, weekends included: v0.1.94 came out on Fri Nov 6 at 16:22Z, after that day's run, and 1.0.0 and 1.1.0 came out on Sun Nov 8. The Engine therefore stays on a skills version several releases old until Monday, and every Engine seat reads that older protocol. The operator asked for weekends to be included (2026-11-08).
The Problem
A weekday-only schedule leaves up to 3 days of skills releases uninstalled, and the gap is widest exactly when the team works through a weekend.
The Architectural Reality
- Design authority: n/a — this changes a schedule and calls no behaviour wrong.
- Dependabot supports a cron schedule:
schedule.interval: cron with schedule.cronjob: "<expression>".
- The file's other policies stay as they are: majors are included, cooldown 3 days with
neo-agent-skills excluded, and grouping.
The Fix
Both ecosystems switch from interval: daily to interval: cron with cronjob: "30 7 * * *", every day at the same morning hour as today. A one-line header note says why daily was not enough.
Decision Record impact: none.
Acceptance Criteria
Out of Scope
Grouping, cooldown and the majors policy. The Brain and Institution repositories each own their own dependabot.yml.
Live latest-open + closed sweep: I read the latest 20 open issues and ran a closed search ("dependabot schedule weekend") at 2026-11-08 20:2xZ; no equivalent was found. Backlog band: 16 open, green.
Origin Session ID: 5ae5ccf8-a6cc-48cc-848a-b1272b67bea5
Context
.github/dependabot.ymlschedules both ecosystems (npm, github-actions) withinterval: daily, which Dependabot runs Monday to Friday only. The dynamicnpm_and_yarn in /.job ran at 07:31Z on Oct 28–30 and Nov 2–6, with no runs on Oct 31, Nov 1, Nov 7 or Nov 8.neo-agent-skillsships one or more versions a day, weekends included: v0.1.94 came out on Fri Nov 6 at 16:22Z, after that day's run, and 1.0.0 and 1.1.0 came out on Sun Nov 8. The Engine therefore stays on a skills version several releases old until Monday, and every Engine seat reads that older protocol. The operator asked for weekends to be included (2026-11-08).The Problem
A weekday-only schedule leaves up to 3 days of skills releases uninstalled, and the gap is widest exactly when the team works through a weekend.
The Architectural Reality
schedule.interval: cronwithschedule.cronjob: "<expression>".neo-agent-skillsexcluded, and grouping.The Fix
Both ecosystems switch from
interval: dailytointerval: cronwithcronjob: "30 7 * * *", every day at the same morning hour as today. A one-line header note says whydailywas not enough.Decision Record impact: none.
Acceptance Criteria
scheduleblocks useinterval: cronandcronjob: "30 7 * * *"; nothing else in the file changes.Out of Scope
Grouping, cooldown and the majors policy. The Brain and Institution repositories each own their own
dependabot.yml.Live latest-open + closed sweep: I read the latest 20 open issues and ran a closed search ("dependabot schedule weekend") at 2026-11-08 20:2xZ; no equivalent was found. Backlog band: 16 open, green.
Origin Session ID: 5ae5ccf8-a6cc-48cc-848a-b1272b67bea5