This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a change to branch use-uv-for-prod-image
in repository https://gitbox.apache.org/repos/asf/airflow.git
discard 904648f718 Update docs/docker-stack/build.rst
discard 9e6e84ea48 Update docs/docker-stack/changelog.rst
discard bdf8eb2f1e Update scripts/docker/install_airflow.sh
discard 8b7013a85b Update docs/docker-stack/build.rst
discard a0628a2314 Update docs/docker-stack/build.rst
discard d54c687280 Update docs/docker-stack/build.rst
discard a96f08e91e Update docs/docker-stack/build.rst
discard 112e0d5756 Update docs/docker-stack/build.rst
discard ac9ac4fba2 Update contributing-docs/testing/k8s_tests.rst
discard 90d91314aa Update contributing-docs/testing/k8s_tests.rst
discard 01155d2026 Switch from --user to venv for PROD image and enable uv
add 2867951ce0 Clarify lack of sync between workers and scheduler (#37913)
add 5390295cdf Switch from --user to venv for PROD image and enable uv
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 (904648f718)
\
N -- N -- N refs/heads/use-uv-for-prod-image (5390295cdf)
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:
Dockerfile | 2 +-
Dockerfile.ci | 2 +-
docs/apache-airflow/core-concepts/overview.rst | 8 ++++++++
3 files changed, 10 insertions(+), 2 deletions(-)