This is an automated email from the ASF dual-hosted git repository.
utkarsharma pushed a change to branch Sync2-10-test
in repository https://gitbox.apache.org/repos/asf/airflow.git
omit bb408fefb2 Update RELEASE_NOTES.rst
omit 123f98f622 Merge branch 'v2-10-stable' into Sync2-10-test
omit 4f2d1d4511 Update RELEASE_NOTES.rst
omit dec731d5cc Update version to 2.10.1.
omit 91f8265b68 Sync v2-10-stable with v2-10-test to release python client
v2.10.0 (#41610)
omit 535f27b137 Make PROD image building works in non-main PRs (#41480)
(#41484) (#41623)
add 6e63e04b68 Skip test_scan_stale_dags_when_dag_folder_change in DB
isolation mode (#41893) (#41895)
add f90750d89a Update version to 2.10.1.
add 7fa94ae30b Update RELEASE_NOTES.rst
add 2d0974e897 Sync v2-10-stable with v2-10-test to release python client
v2.10.0 (#41610)
add 3009e26914 Update RELEASE_NOTES.rst
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 (bb408fefb2)
\
N -- N -- N refs/heads/Sync2-10-test (3009e26914)
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:
tests/dag_processing/test_job_runner.py | 1 +
1 file changed, 1 insertion(+)
