chore(config): point the mongodb-5.2.x ci_rerun target at PR 622 - #72
Open
aclark4life wants to merge 1 commit into
Open
chore(config): point the mongodb-5.2.x ci_rerun target at PR 622#72aclark4life wants to merge 1 commit into
aclark4life wants to merge 1 commit into
Conversation
PR 607 (INTPYTHON-528 Backports for 5.2.4 LTS) merged 2026-08-21 along with the 5.2.4 release, so the mapping pointed at a merged PR. `dbx sync django -B mongodb-5.2.x` would have hit the stale-mapping guard and reported "PR is merged — skipping" instead of re-running anything. PR 622 (INTPYTHON-1077 5.2.5 LTS backports, base 5.2.x) succeeds it as the 5.2.x head PR for the 5.2 LTS window, which runs to ~April 2028. Note that 622 is currently a draft with no commits of its own, so until it has a first CI run there are no workflow runs to re-queue; the mapping is correct but inert until then.
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
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.
Why
ci_rerunmappedmongodb-5.2.xto PR 607 ("INTPYTHON-528 Backports for 5.2.4 LTS"), which merged 2026-08-21 with the 5.2.4 release. A mapping pointing at a merged PR is a stale-config bug:dbx sync django -B mongodb-5.2.xwould hit the guard and printinstead of re-running anything, so a rebase that broke the adapted 5.2 tests would go unnoticed.
What
Point it at PR 622 ("INTPYTHON-1077 5.2.5 LTS backports", base
5.2.x), which succeeds 607 as the 5.2.x head PR for the 5.2 LTS window (upstream security/data-loss fixes run to ~April 2028). Comment records the supersession, matching the existing 535→602 note in the same block.Note
PR 622 is currently a draft with no commits of its own. Drafts report
state: OPENso it passes the open-PR check, but_rerun_pr_cire-runs existing workflow runs on the head commit — with no commits there are no runs to re-queue. The mapping is correct but inert until 622 gets a first commit and CI run.Testing
475 tests pass; TOML check clean. Config-only change, no code paths touched.
Not in scope
The
mongodb-6.1.x↔mongodb-6.2.xswap in the same block is still pending — backendmainis6.2.0.dev0but its CI still clonesmongodb-6.1.x, and that has to be repointed upstream first. Tracked separately.