ci: Friday release train (L2, @agentage dep-bump) - #270
Merged
Conversation
Contributor
|
🎉 PR Validation ✅ PASSED Commit: Checks:
Ready to merge! ✨ 🔗 View workflow run |
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 MINOR release train for @agentage/cli, replacing the manual
release-prepare.yml.What
release-train.yml(supersedesrelease-prepare.yml, removed): scheduled Friday, auto dep-bump + minor bump + verify + auto-merge PR + explicitpublish.ymldispatch. No human step on the happy path.@agentage/memory-core+@agentage/server-memory(release 20:00/21:00 Prague), so this train runs at 22:00 Prague. Crons0 20 * * 5+0 21 * * 5; gate proceeds only whenTZ=Europe/Prague date +%H== 22 (DST-proof).npx npm-check-updates -u --filter '@agentage/*'+npm installbefore the version bump. Dep changes alone justify a release; skips only when neither releasable commits (excl. docs/ci/plain-chore; chore(deps) counts) nor dep changes exist.scripts/bump-version.js minor.npm run verifyafter the dep bump is the integration gate (red = fail without releasing).publish.yml(gh workflow run --ref master) since GITHUB_TOKEN merges don't fire push triggers.permissions: actions: write.Bug fixes
RELEASE_PAT || PAT_TOKEN || GITHUB_TOKEN+ origin re-auth to fire downstream checks. New train uses plain GITHUB_TOKEN with the--auto --squash-> direct-squash 'clean status' fallback + explicit publish dispatch, removing the PAT dependency entirely.^chore\(release\)(and workflow_dispatch always allows) - no change needed; the train's commit subjectchore(release): X.Y.Zpasses it.Dependabot
ignoresemver-major rule; config now matches org standard (weekly Fri 18:00 Europe/Prague, assignees ['vreshch'], group '*', limits 10 npm / 5 gh-actions).Verified locally:
npm ci+npm run verifygreen; all YAMLyaml.safe_load-valid.