This is an automated email from the ASF dual-hosted git repository.
shahar1 pushed a change to branch drop-py310/7-pyproject-metadata
in repository https://gitbox.apache.org/repos/asf/airflow.git
discard 2a5090a5d56 Keep Breeze's locked dependency versions when dropping
Python 3.10
discard 4807cf067a6 Drop the Python 3.10 provider metadata shim and regenerate
datamodels
discard 7308c1acd79 Require Python 3.11 in all distributions
discard 530f2f6d39b Apply ruff Python 3.11 fixes to dev tooling, scripts and
test suites
add cea018f5cb7 Apply ruff Python 3.11 fixes to dev tooling, scripts and
test suites
add 76bc216de6b Require Python 3.11 in all distributions
add e16129f6797 Drop the Python 3.10 provider metadata shim and regenerate
datamodels
add 2f7f0d75b87 Keep Breeze's locked dependency versions when dropping
Python 3.10
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (2a5090a5d56)
\
N -- N -- N refs/heads/drop-py310/7-pyproject-metadata
(2f7f0d75b87)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
