This is an automated email from the ASF dual-hosted git repository.
maximebeauchemin pushed a change to branch supersetbot-bump-croniter
in repository https://gitbox.apache.org/repos/asf/superset.git
discard d768a6779a fixin'
discard b69541c4c6 chore(🦾): bump python croniter 2.0.3 -> 2.0.5
add 3f5ffc7026 chore(🦾): bump python flask-caching 2.1.0 -> 2.3.0 (#28463)
add e8ba5045d9 chore(🦾): bump python markdown subpackage(s) (#28464)
add 62b1757b07 chore(🦾): bump python flask-migrate subpackage(s) (#28465)
add 908a9bbb4c chore(🦾): bump python flask-session subpackage(s) (#28472)
add fedd24522c chore(🦾): bump python cryptography 42.0.5 -> 42.0.7 (#28468)
add 9d628349c7 chore(🦾): bump python croniter 2.0.3 -> 2.0.5
add f253829da5 fixin'
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 (d768a6779a)
\
N -- N -- N refs/heads/supersetbot-bump-croniter (f253829da5)
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 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
