Basemap test was erroring on the first go for node 21, but it passed after 2 retries.

Do you think we should update the package-lock.json as well (since that's what should ensure consistent installs when cloning/running locally), or just updating the package.json are enough? cc @domoritz

• package-lock.json should be updated. If we run npm ci it should error when the locale is not up to date
• remove any kind of deployment scripts for the website so that we don't accidentally override the current version. We also should not push schema updates.

We can make those changes on the maintenance branch rather than this pull request.

We can make those changes on the maintenance branch

Thanks @domoritz , I wasn't sure if we need to update package-lock.json right away to get the unit tests to use the latest code on branch rather than downloading from NPM. If the current diff is ready for use, then I'll leave it to you and Lukas re: releasing these updates to the non-ESM version of Vega.

Before making a release, we need to check the scripts to delete anything that would override release artifacts like the schema or website.

But happy to merge this pr as is.

Fair enough. FWIW from what I can see the docs site deploy only runs on the main branch, so merges to this long-term-support branch should be unaffected. I'm less clear on where the "publish new schema" script would live.

https://github.com/vega/vega/actions/runs/18161260314

Let's merge this PR then if we're all set from the Kibana side.

We should delete anything that may release.