ci: Friday release train (L1, memory-core dep-bump) - #19
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.
Fully automated Friday release train for @agentage/server-memory (Level 1, dep-driven).
What
.github/workflows/release-train.yml: weekly Friday 21:00 Europe/Prague MINOR release to npm..github/dependabot.yml: dropped the semver-majorignoreblock to match the org standard (all updates come through, just grouped).Train shape (mirrors find-mcp)
0 19 * * 5,0 20 * * 5); Prague-hour gate proceeds only whenTZ=Europe/Prague date +%H== 21 (runs after memory-core's 20:00 train so it can pull the fresh core).@agentage/*dep to latest vianpm-check-updates-> a dep change ALONE justifies releasing -> MINOR bump package.json ->npm run verifyas the integration gate against the bumped memory-core (red verify fails the train, PR stays open) -> create + auto-merge release PR -> dispatchpublish.yml(GITHUB_TOKEN merges never fire push triggers).permissions: actions: writeso the train can dispatch publish.yml.publish.yml already accepts
chore(release): X.Y.Zandworkflow_dispatch- no change needed.Verified locally:
npm ci+npm run verifygreen; all YAML validated withyaml.safe_load.