This is an automated email from the ASF dual-hosted git repository.
dependabot[bot] pushed a change to branch
dependabot/pip/flightsql-dbapi-gte-0.2.2-and-lt-0.3
in repository https://gitbox.apache.org/repos/asf/superset.git
discard 8d9a5b9934c chore(deps-dev): update flightsql-dbapi requirement
add d4652460eed chore(deps-dev): bump google-cloud-bigquery from 3.42.1 to
3.42.2 (#42422)
add 8864b7a0a31 chore(deps-dev): update oracledb requirement from
<5,>=2.0.0 to >=4.0.2,<5 (#42421)
add 9d6fbdceff8 chore(deps-dev): update ibm-db-sa requirement from
<=0.4.4,>0.3.8 to <=0.4.4,>=0.4.4 (#42419)
add 7c5b2270333 chore(deps-dev): update flightsql-dbapi requirement
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 (8d9a5b9934c)
\
N -- N -- N
refs/heads/dependabot/pip/flightsql-dbapi-gte-0.2.2-and-lt-0.3 (7c5b2270333)
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:
pyproject.toml | 6 +++---
requirements/development.txt | 4 ++--
2 files changed, 5 insertions(+), 5 deletions(-)
