(superset) branch supersetbot-bump-flask-session updated (261548edc0 -> 1e4cad576b)

[ma...@apache.org]

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

maximebeauchemin pushed a change to branch supersetbot-bump-flask-session
in repository https://gitbox.apache.org/repos/asf/superset.git


 discard 261548edc0 Merge branch 'supersetbot-bump-flask-session==0.8.0' into supersetbot-bump-flask-session
    omit fb134dba36 try noqa
    omit 649feda138 deprecating SESSION_USE_SIGNER
    omit 174c89927d chore(🦾): bump python flask-session==0.8.0
 discard dff24ad668 chore(🦾): bump python flask-session 0.5.0 -> 0.8.0
     add 96dde34cdc chore(🦾): bump python gevent 23.9.1 -> 24.2.1 (#27728)
     add 9065a4e7d2 chore(🦾): bump python google-cloud-bigquery 3.10.0 -> 3.20.0 (#27752)
     add 70da454bbc fix: reduce alert error to warning (#27744)
     add 9f55f4acc3 chore(🦾): bump python flask-session 0.5.0 -> 0.8.0
     add 0c4aff6e37 deprecating SESSION_USE_SIGNER
     add 1e4cad576b try noqa

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   (261548edc0)
            \
             N -- N -- N   refs/heads/supersetbot-bump-flask-session (1e4cad576b)

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/development.txt      | 27 +++++++++++++++++----------
 superset/commands/report/alert.py |  2 +-
 2 files changed, 18 insertions(+), 11 deletions(-)