thanks @chaigh-uk - I'll try to prioritize review in the next cycle.

@chaigh-uk Thanks very much for the PR.

You could fetch upstream/master and then add a test titled publish-dist-node-v22 to regenerate plot-schema similar to publish-dist.

publish-dist is declared at

You also need to add your new publish-dist-node-v22 test below here:

Thank you!

@chaigh-uk Thanks very much for the PR.

You could fetch upstream/master and then add a test titled publish-dist-node-v22 to regenerate plot-schema similar to publish-dist.

publish-dist is declared at

plotly.js/.circleci/config.yml

Line 410 in 40f2221

publish-dist:

You also need to add your new publish-dist-node-v22 test below here:

plotly.js/.circleci/config.yml

Line 553 in 40f2221

- publish-dist

Thank you!

Thanks for taking a look @archmoj - I've had a go at this in 46e0277
Hopefully I've understood correctly, but let me know if I've missed anything 👍

💯 🙏 Many thanks @chaigh-uk for the smart addition of node 22 tests.

It is interesting to see node v22 tests appear to run faster.
The failing baseline tests (listed https://app.circleci.com/pipelines/github/plotly/plotly.js/11881/workflows/222c9105-1ddf-48c3-8268-a66cbfc281c3) are not related to this PR.

It would be great if someone else from @plotly/plotly_js also help approve this PR.

On another note @chaigh-uk used a pattern in 46e0277 that simplified testing in different container versions.

IMHO - It would be of interest to apply similar pattern in other places in plotly.js and plotly.py and dash tests to reduce/avoid duplicated CircleCI config code
cc: @alexcjohnson @antoinerg @samhinshaw