Conversation
Replaces the single weekly-merge workflow with the freeze/release-PR/unfreeze lifecycle established in mindshub_inference#319: staging-freeze locks staging on a weekly cron, weekly-merge-staging opens the staging->main release PR, and staging-unfreeze unlocks staging when the release PR merges. Branch-protection changes go through a shared set-branch-lock.js helper using RELEASE_AUTOMATION_TOKEN. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…orkflows Replaces the self-contained freeze/release-PR/unfreeze workflows and the set-branch-lock.js helper with ~15-line callers of the reusable workflows in mindsdb/github-actions (see mindsdb/github-actions#32). Workflow names are preserved so the workflow_run chain still fires. Auth now uses the mindsdb-release-train GitHub App (minted per-job in the reusable workflows) instead of a PAT; freeze/unfreeze toggle the pre-provisioned staging-freeze ruleset instead of round-tripping branch protection. The unfreeze caller carries the merged-release-PR + fork-PR guard. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Adds a top-level 'permissions: contents: read' block to each caller so the GITHUB_TOKEN is least-privilege (fixes CodeQL actions/missing-workflow-permissions). All privileged operations run through the mindsdb-release-train App token, so contents: read is sufficient for the callers. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…eeze) Follows the rename in mindsdb/github-actions#32. Caller filenames and workflow names are unchanged; only the uses: target paths move. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Add weekly release cycle workflows (freeze, release PR, unfreeze)
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Back-merges
mainintostagingso staging picks up the weekly release cycle workflows (#220).Commits carried: the #220 branch commits and merge commit (freeze/release-PR/unfreeze callers, reusable-workflow refactor, token permissions, SHA pins).
Merge this with a merge commit (not squash) — this repo allows it — so staging and main share history and this diff doesn't reappear next cycle.
🤖 Generated with Claude Code