ephraimbuddy commented on a change in pull request #20962:
URL: https://github.com/apache/airflow/pull/20962#discussion_r808059432
##########
File path: dev/README_RELEASE_AIRFLOW.md
##########
@@ -205,6 +205,7 @@ The Release Candidate artifacts we vote upon should be the
exact ones we vote ag
- Add a commit that updates `CHANGELOG.md` to add changes from previous
version if it has not already added.
For now this is done manually, example run `git log --oneline v2-2-test..HEAD
--pretty='format:- %s'` and categorize them.
- Add section for the release in `UPDATING.md`. If no new entries exist, put
"No breaking changes" (e.g. `2.1.4`).
+- Update the `REVISION_HEADS_MAP` at airflow/utils/db.py to include the
revision head of the release even if there are no migrations.
Review comment:
Looks good, I think the challenge would be to get the migration heads of
the versions and discard every other migration in-between when going from
version to version. It's still necessary to have a pre-commit or a ci job that
makes sure we have the migration head updated before a release
--
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]
