This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch supersetbot-bump-flask-sqlalchemy
in repository https://gitbox.apache.org/repos/asf/superset.git
omit 6cbcbd0e13 chore(🦾): bump python flask-sqlalchemy subpackage(s)
add a80803566d chore(🦾): bump python marshmallow 3.21.2 -> 3.23.1 (#31045)
add 8c1c2570b3 chore(🦾): bump python nh3 0.2.17 -> 0.2.18 (#31054)
add 078257dd1b docs: updated the install process in pypi.mdx (#31044)
add d69da5f0f5 chore(🦾): bump python flask-wtf 1.2.1 -> 1.2.2 (#31052)
add bf42ea70ba chore(🦾): bump python cron-descriptor 1.4.3 -> 1.4.5
(#31046)
add f180d00775 chore(🦾): bump python flask-sqlalchemy 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 (6cbcbd0e13)
\
N -- N -- N refs/heads/supersetbot-bump-flask-sqlalchemy
(f180d00775)
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:
docs/docs/installation/pypi.mdx | 11 ++++++-----
requirements/base.txt | 10 +++++-----
2 files changed, 11 insertions(+), 10 deletions(-)
