This is an automated email from the ASF dual-hosted git repository.
maximebeauchemin pushed a change to branch bump_python311
in repository https://gitbox.apache.org/repos/asf/superset.git
omit d3654cbc1f trying older pandas
omit 1099a66d11 bump tabulate
omit ef9d769bb6 cleanup
omit 463656cf3e newer pandas
omit 34efd58e92 rm --only-binary
omit e370a49871 more tries
omit adaf370c0e trying things
omit b89442daef skip build essentials
omit 727a06a498 3.11
omit c9ceb8134e bumping more libs
omit 015b98f729 bumping libs
omit d859e9b6fb bumped numpy
omit 5dfc5d62d4 given 3.12 another shot
add fea3210fb6 current=3.11, previous=3.10, next=void for now
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 (d3654cbc1f)
\
N -- N -- N refs/heads/bump_python311 (fea3210fb6)
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/actions/setup-backend/action.yml | 8 +--
.github/workflows/pre-commit.yml | 2 +-
.../workflows/superset-python-integrationtest.yml | 2 +-
.github/workflows/superset-python-unittest.yml | 2 +-
pyproject.toml | 9 ++--
requirements/base.in | 3 --
requirements/base.txt | 38 +++++--------
requirements/development.txt | 63 +++++++++++-----------
8 files changed, 54 insertions(+), 73 deletions(-)
