Skip to content

ci: add the weekly release-train workflows - #12503

Closed
pnewsam wants to merge 1 commit into
mainfrom
release-train-workflows
Closed

pnewsam wants to merge 1 commit into
mainfrom
release-train-workflows

Conversation

@pnewsam

@pnewsam pnewsam commented Oct 19, 2026

Copy link
Copy Markdown
Contributor

Description

Adds mindshub to the weekly staging → main release, the same process the service repos use:

  • Staging Freeze (Fridays, 13:47 UTC) locks staging.
  • Create staging to main release PR opens the release PR once the freeze lands.
  • Staging Unfreeze unlocks staging when the release PR merges, then syncs main back into it.
  • Sync main to staging merges main into staging after any other push to main, such as a hotfix.

Each file is a small wrapper around a shared workflow in mindsdb/github-actions, copied from scratchpad-controller. There's one real change: the release PR job runs only after the freeze. The service repos also refresh it after each staging deploy, but mindshub has no staging deploy. Use workflow_dispatch to see what's queued mid-week.

After this merges, work goes to staging and reaches main once a week. Docs changes count too, because deploy_docs.yml publishes from main. Urgent docs fixes can still go straight to main as hotfixes; the sync carries them back to staging.

Merge order:

  1. chore: merge main into staging to reconcile the branches #12502, so staging already contains main.
  2. The org admin setup: install the release-train App, give this repo access to its org variable and secret plus the Slack secrets, and set the staging_frozen property to false. Until that's done, every one of these workflows fails and posts an alert to Slack.
  3. This PR, targeting main. Scheduled triggers only run from the default branch.

Type of change

  • ⚡ New feature (non-breaking change which adds functionality)

Verification Process

  • Test Location: Specify the URL or path for testing.

  • Verification Steps: Outline the steps or queries needed to validate the change. Include any data, configurations, or actions required to reproduce or see the new functionality.

  • python3 scripts/workflow_graph.py --workflow-dir <mindshub>/.github/workflows (from github-actions): the new workflows add no errors. It reports one error that was already there: codeql.yml and deploy_docs.yml both run on push to main. This PR leaves that alone.

  • All workflow YAML parses.

  • Not run: the workflows themselves. They can't run until the admin setup is done. After merging: run Staging Freeze by hand, check that a push to staging is refused, then merge the release PR and check that the unfreeze and the sync both succeed.

Additional Media:

  • I have attached a brief loom video or screenshots showcasing the new functionality or change.

Checklist:

  • My code follows the style guidelines(PEP 8) of MindsDB.
  • I have appropriately commented on my code, especially in complex areas.
  • Necessary documentation updates are either made or tracked in issues.
  • Relevant unit and integration tests are updated or added.

🤖 Generated with Claude Code

Add the four wrappers the service repos use to run the weekly staging ->
main release: the Friday freeze, the release PR, the unfreeze when that
PR merges, and the main -> staging sync after any other push to main.
Each calls the shared reusable in mindsdb/github-actions.

The release PR wrapper fires on the freeze alone. mindshub has no
staging deploy pipeline to refresh it mid-week, so that trigger is
dropped from the copy.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@pnewsam

pnewsam commented Nov 3, 2026

Copy link
Copy Markdown
Contributor Author

Closed in favor of merging PRs directly to main

@pnewsam pnewsam closed this Nov 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant