This is an automated email from the ASF dual-hosted git repository.
beto pushed a change to branch sc_74037
in repository https://gitbox.apache.org/repos/asf/superset.git
omit 18181b4307 Improve test
omit 7ba1c6de6b Small fix
omit 2efe150574 Add tests
omit 2ee72fb65e fix: smarter date formatter
add f6ce40d246 chore: upgrade node to most recent 16.x (#25362)
add 52eba11d6a docs: update docker-compose to match latest release
(#25332)
add 296ff17f19 fix: preventing save button from flickering in SQL Lab
(#25106)
new 9643b06ab9 fix: smarter date formatter
new 411c21f33b Add tests
new 1c1992e7f8 Small fix
new 1a55007b72 Improve test
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 (18181b4307)
\
N -- N -- N refs/heads/sc_74037 (1a55007b72)
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.
The 4 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
.../installing-superset-using-docker-compose.mdx | 15 +++++++--------
superset-frontend/.nvmrc | 2 +-
superset-frontend/package.json | 4 ++--
.../SqlLab/components/SaveQuery/SaveQuery.test.tsx | 21 ++++++++++++++++++++-
.../src/SqlLab/components/SaveQuery/index.tsx | 12 ++++++++----
5 files changed, 38 insertions(+), 16 deletions(-)
