This is an automated email from the ASF dual-hosted git repository.

jedcunningham pushed a change to branch v3-0-test
in repository https://gitbox.apache.org/repos/asf/airflow.git


 discard 6655e87ee6d Bump version of kubernetes provider to 10.4.0
 discard f97fe6287e9 Bump version of celery provider to 3.11.0
 discard a1b317af730 Bump version of standard provider to 1.0.0
 discard ab8f6615ca0 Bump task-sdk version to 1.0.0.alpha4
     new f0524db873e Bump task-sdk version to 1.0.0.b1
     new 286987bbbb5 Bump version of standard provider to 1.0.0
     new beca634ab34 Bump version of celery provider to 3.11.0
     new bcd82b9c5a7 Bump version of kubernetes provider to 10.4.0

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   (6655e87ee6d)
            \
             N -- N -- N   refs/heads/v3-0-test (bcd82b9c5a7)

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.

The 4 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 task_sdk/src/airflow/sdk/__init__.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Reply via email to