This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch supersetbot-bump-selenium
in repository https://gitbox.apache.org/repos/asf/superset.git
discard 311e642816 chore(🦾): bump python selenium 3.141.0 -> 4.9.1
add 339d491dfc feat(sqllab): Popup notification when download data can
exceed row count (#31187)
add deec63bb5b docs(contributing): how to nuke the docker-compose postgres
(#31186)
add 8020729ced fix: check for column before adding in migrations (#31185)
add 3564740255 chore: pin greenlet in base dependencies (#31254)
add 8ea23bc323 chore(🦾): bump python selenium 3.141.0 -> 4.9.1
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 (311e642816)
\
N -- N -- N refs/heads/supersetbot-bump-selenium (8ea23bc323)
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/contributing/development.mdx | 18 ++++++++++
pyproject.toml | 8 ++---
requirements/base.txt | 1 +
.../SqlLab/components/ResultSet/ResultSet.test.tsx | 40 +++++++++++++++++++++-
.../src/SqlLab/components/ResultSet/index.tsx | 20 ++++++++++-
superset/migrations/shared/utils.py | 15 ++++++++
...4-01_22-44_c22cb5c2e546_user_attr_avatar_url.py | 7 ++--
...-04-11_15-41_5f57af97bc3f_add_catalog_column.py | 4 ++-
...0-52_58d051681a3b_add_catalog_perm_to_tables.py | 5 +--
9 files changed, 107 insertions(+), 11 deletions(-)
