This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch supersetbot-bump-flask-migrate
in repository https://gitbox.apache.org/repos/asf/superset.git
omit 44846024af chore(🦾): bump python flask-migrate subpackage(s)
add 55f0713a2f chore(🦾): bump python mako 1.3.5 -> 1.3.6 (#31097)
add e3bdfb5def chore(🦾): bump python sshtunnel subpackage(s) (#31092)
add 40fe05c5e2 chore(🦾): bump python jsonpath-ng 1.6.1 -> 1.7.0 (#31093)
add 9067371234 chore(🦾): bump python chardet 5.1.0 -> 5.2.0 (#31094)
add 0d346d4414 chore(🦾): bump python pytest-cov 5.0.0 -> 6.0.0 (#31096)
add 043c585008 chore(🦾): bump python pyproject-api 1.6.1 -> 1.8.0 (#31098)
add cf134ab3aa chore(🦾): bump python wheel 0.43.0 -> 0.45.1 (#31099)
add c4a56c3f6e chore(🦾): bump python sqloxide 0.1.43 -> 0.1.51 (#31100)
add 83924f7e10 chore(🦾): bump python pluggy 1.4.0 -> 1.5.0 (#31101)
add ca63760a4b chore(🦾): bump python markdown 3.6 -> 3.7 (#31102)
add a505b6c380 chore(🦾): bump python flask-migrate subpackage(s)
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 (44846024af)
\
N -- N -- N refs/heads/supersetbot-bump-flask-migrate
(a505b6c380)
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/bump-python-package.yml | 11 ++++++++++-
requirements/base.txt | 8 ++++----
requirements/development.txt | 14 +++++++-------
3 files changed, 21 insertions(+), 12 deletions(-)
