Copilot commented on code in PR #62343:
URL: https://github.com/apache/airflow/pull/62343#discussion_r3025380679
##########
airflow-core/src/airflow/utils/db.py:
##########
@@ -115,7 +115,7 @@ class MappedClassProtocol(Protocol):
"3.0.3": "fe199e1abd77",
"3.1.0": "cc92b33c6709",
"3.1.8": "509b94a1042d",
- "3.2.0": "1d6611b6ab7c",
+ "3.2.0": "a7e6d4c3b2f1",
"3.3.0": "a4c2d171ae18",
Review Comment:
The `_REVISION_HEADS_MAP` entry for `3.2.0` now points to revision
`a7e6d4c3b2f1`, but that revision’s migration file declares `down_revision =
"a4c2d171ae18"` (a `3.3.0` migration). This makes the mapping non-monotonic
(`3.2.0` > `3.3.0`) and will break logic that relies on version→head ordering.
The new migration should be mapped to the *next* Airflow version after `3.3.0`
(and `3.2.0` should continue to map to `1d6611b6ab7c`).
```suggestion
"3.2.0": "1d6611b6ab7c",
"3.3.0": "a7e6d4c3b2f1",
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
