Uh oh!
There was an error while loading. Please reload this page.
promote: cross-repo change guidance (develop -> main) - #112
Merged
Conversation
The train promotes each repo independently (fail-fast: false, no ordering), so a hop routinely merges some repos and holds others -- the 2026-07-29 prod hop merged 8 of 10. Nothing today stops averaging-service promoting a change that needs a backend change backend has not shipped yet, and backend can be held by something unrelated to that work. Measured while looking into this: only 1 of 17 epics on the board spans repos, so the ticket graph does not encode these dependencies and cannot be gated on. The durable fix is not orchestration but compatibility -- expand, adopt, contract -- which removes the dependency on promotion timing rather than managing it. - README: a Cross-repo changes section with the three-step pattern and what to do when a change is genuinely breaking. - Org PR template: a checklist line pointing at it. Deliberately does NOT document repos.yml atomic groups; those do not exist yet. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
docs: expand-then-contract for cross-repo changes
LukasWodka
commented
Jul 31, 2026
ContributorAuthor
👋 Heads-up — Code review queue is at 33 / 30 Above the WIP limit. The team convention is to review existing PRs before opening new work. Open PRs currently in Code review (oldest first):
Pull from review before opening new work. (This is a nudge from the kanban WIP check, not a block.) |
LukasWodka
commented
Jul 31, 2026
ContributorAuthor
bugbot run |
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit fe4681f. Configure here.
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Promotes #111 — the Cross-repo changes README section (expand → adopt → contract) and the matching PR-template checklist line.
Docs-only, per the docs exception for this repo. Content already reviewed and Bugbot-clean on #111.
Note
Low Risk
Documentation and PR template text only; no runtime, config, or workflow behavior changes.
Overview
Adds org-wide documentation for coordinating changes across repos when the release train promotes each repository independently.
The README gains a Cross-repo changes section explaining why you cannot assume the fleet moves together, the expand → adopt → contract rollout pattern, and how to handle unavoidable breaking changes (Breaking change checkbox, deployment notes with owner-qualified PR refs, manual hop sequencing).
The PR template checklist gains a matching item: either ship expand-then-contract or document breaking rollout in Deployment notes.
Reviewed by Cursor Bugbot for commit fe4681f. Bugbot is set up for automated code reviews on this repo. Configure here.