This is an automated email from the ASF dual-hosted git repository.
rusackas pushed a change to branch bump-node-engine
in repository https://gitbox.apache.org/repos/asf/superset.git
discard 742588501d fix: Add d3 modules to Jest transformIgnorePatterns
discard a522bf6e49 fix: resolve TypeScript errors in CI build
discard 9ace9d5c6c tweak
discard 736dfb31d7 chore(npm): bump node engine, build fresh package-lock.json
add 2f8939d229 fix(native filters): throws an error when a chart
containing a bigint value (#34539)
add 7b6a5c5ba7 chore(npm): bump node engine, build fresh package-lock.json
add d7138c7b68 tweak
add 7c0e81d222 fix: resolve TypeScript errors in CI build
add 2d89ea45bc fix: Add d3 modules to Jest transformIgnorePatterns
add dcd46d6116 fix(jest): Override query-string to v7.1.3 to fix
CommonJS/ESM compatibility
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 (742588501d)
\
N -- N -- N refs/heads/bump-node-engine (dcd46d6116)
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:
superset-frontend/package-lock.json | 55 ++++++++++++----------
superset-frontend/package.json | 3 +-
.../FiltersConfigForm/FiltersConfigForm.tsx | 2 +-
.../FiltersConfigModal/FiltersConfigModal.test.tsx | 44 +++++++++++++++++
4 files changed, 77 insertions(+), 27 deletions(-)
