(superset) branch supersetbot-bump-importlib-metadata updated (4e9cc9b63e -> 16a85d5e75)

[gi...@apache.org]

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

github-bot pushed a change to branch supersetbot-bump-importlib-metadata
in repository https://gitbox.apache.org/repos/asf/superset.git


 discard 4e9cc9b63e chore(🦾): bump python importlib-metadata subpackage(s)
     add e76a6ed63d chore(🦾): bump python flask-compress subpackage(s) (#33800)
     add b376459e8c chore(🦾): bump python click 8.2.0 -> 8.2.1 (#33796)
     add 28b4f44baa chore(🦾): bump python flask subpackage(s) (#33797)
     add dc32608fa3 chore(🦾): bump python flask-wtf subpackage(s) (#33799)
     add 3591e362e3 chore(🦾): bump python shillelagh subpackage(s) (#33793)
     add d2e6249ce2 chore(🦾): bump python flask-session subpackage(s) (#33792)
     add f2f1ea948c chore(🦾): bump python sqlglot 26.17.1 -> 26.28.1 (#33798)
     add a1cbd2578e chore(🦾): bump python flask-caching subpackage(s) (#33795)
     add 16a85d5e75 chore(🦾): bump python importlib-metadata 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   (4e9cc9b63e)
            \
             N -- N -- N   refs/heads/supersetbot-bump-importlib-metadata (16a85d5e75)

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:
 requirements/base.txt        | 18 +++++++++---------
 requirements/development.txt | 18 +++++++++---------
 2 files changed, 18 insertions(+), 18 deletions(-)