potiuk opened a new pull request #14120: URL: https://github.com/apache/airflow/pull/14120
This change enables easy switching between GitHub Package Registry and GitHub Container Registry by simply adding GITHUB_REGISTRY secret to be either `docker.package.github.com` or `ghcr.io`. This makes it easy to switch only by the Apache Airflow repository run builds, as it requires preparation of images (to make them public and to add permissions to manage them) after they got created for the first time. GitHub Package Registry works out-of-the-box but it is less stable and considered a legacy, also it does not allow image retention. Documentation has been updated to reflect the reasoning of choosing this solution as well as describing maintenance processes around images (including adding new Python version) <!-- Thank you for contributing! Please make sure that your code changes are covered with tests. And in case of new features or big changes remember to adjust the documentation. Feel free to ping committers for the review! In case of existing issue, reference it using one of the following: closes: #ISSUE related: #ISSUE How to write a good git commit message: http://chris.beams.io/posts/git-commit/ --> --- **^ Add meaningful description above** Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#pull-request-guidelines)** for more information. In case of fundamental code change, Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals)) is needed. In case of a new dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). In case of backwards incompatible changes please leave a note in [UPDATING.md](https://github.com/apache/airflow/blob/master/UPDATING.md). ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
