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

asorokoumov pushed a change to branch dependabot/uv/pyasn1-0.6.3
in repository https://gitbox.apache.org/repos/asf/otava.git


 discard a3da2c0  Bump pyasn1 from 0.6.2 to 0.6.3
     add 54317df  Fix --config-file parser broken by configargparse 1.7.3
     add d11bdea  Merge pull request #138 from apache/fix-config-file
     add c90837b  INFRA-27784 Update setup-up version in CI (#147)
     add 3ed9c32  Bump protobuf from 6.33.0 to 6.33.5 (#133)
     add 4a1eb1b  Bump pyasn1 from 0.6.2 to 0.6.3

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   (a3da2c0)
            \
             N -- N -- N   refs/heads/dependabot/uv/pyasn1-0.6.3 (4a1eb1b)

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:
 .github/workflows/python-app.yml |   4 +-
 otava/config.py                  |   8 +++
 otava/main.py                    |  18 ++---
 tests/cli_help_test.py           | 139 +++++++++++++++------------------------
 tests/postgres_e2e_test.py       |   4 +-
 uv.lock                          |  18 ++---
 6 files changed, 85 insertions(+), 106 deletions(-)

Reply via email to