ci: Friday release train (L0) - #23
Merged
Merged
Conversation
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
Adds a fully automated Friday MINOR release train for
@agentage/memory-core, ported from the provenfind-mcppattern and simplified for this Level 0 package (no internal@agentagedeps, npm-only surface, no MCP registry /server.json).release-train.ymlRuns weekly and cuts a release with no human step on the happy path:
0 18 * * 5and0 19 * * 5) cover both offsets; the gate job keeps only the run where the local Prague hour is20, so the train always fires at 20:00 Europe/Prague regardless of DST.release/*PR, detects releasable commits since the last tag (docs/ci/plain-chore excluded,chore(deps)counts), always does a minor bump ofpackage.json(+ lockfile vianpm install --package-lock-only), runsnpm run verify, opens thechore(release): X.Y.ZPR, and auto-merges it (squash).publish.yml.Why the explicit publish dispatch (GITHUB_TOKEN rationale)
A merge performed with the default
GITHUB_TOKENdoes not trigger other workflows, sopublish.yml'spushtrigger never fires from the auto-merge. The train therefore dispatchespublish.ymlexplicitly after merging, which requirespermissions: actions: writeon this workflow.publish.ymlalready treatsworkflow_dispatchas a release and its release-gate regex already acceptschore(release): X.Y.Z, so no change was needed there.dependabot.ymlRemoved the nonstandard
ignore(semver-major) rule to match the org standard - all updates, including majors, come through grouped. Schedule, assignees, group, and PR limits already matched.Friday 20:00 Prague slot
Deliberately after the dependabot Friday 18:00 Europe/Prague run, giving triage a window to land the weekly dependency bundle before the train departs.
Verification
npm ci+npm run verifypass locally (165 tests). All workflow + dependabot YAML validated withyaml.safe_load.