This is an automated email from the ASF dual-hosted git repository.
ephraimanierobi pushed a change to branch v2-10-test
in repository https://gitbox.apache.org/repos/asf/airflow.git
discard a29d85a71b Test: set fail-fast to false for prod image building
discard a11754512a Update RELEASE_NOTES.rst
discard f9ab56a964 Regenerate breeze command svgs
discard c594c371b0 Update version to 2.10.0
discard 1c6a5d0ff5 Update default branches for 2-10
add a9d6d2a03e Change fail-fast to false for prod image building workflow
(#41023)
add 14e9759f6a Bump google-cloud-sdk version to 485.0.0 in Breeze scripts
(#41024)
add 96c5ada160 Update default branches for 2-10
add 3948615cd2 Update version to 2.10.0
add 5426e88d43 Update RELEASE_NOTES.rst
add 56068df2ed regenerate command hashes
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 (a29d85a71b)
\
N -- N -- N refs/heads/v2-10-test (56068df2ed)
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:
scripts/in_container/bin/install_gcloud.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
