Zhe Sun

package.json got updated unexpectedly with mvn command

8

### Description of the bug / feature the package.json got updated unexpectedly with mvn command ### Minimal reproducible example ``` git clone [email protected]:vaadin/docs.git cd docs git checkout v21 mvn install...

currently they are muted in the [Teamcity](https://teamcity.vaadin.com/viewLog.html?buildId=90574&tab=buildResultsDiv&buildTypeId=Vaadin7Framework_ActiveProjects_FrameworkGitHubValidationBuild20&logTab=) it looks the failure comes even before the screenshot comparison.

`23.2.0.beta1` has been released. the following issues need to be addressed. - hilla dependency versions have been wrongly upgrade in package.json in docs repo - PR looks like [this](https://github.com/vaadin/docs/pull/1620/files) and...

fixes https://github.com/vaadin/testbench/issues/1321 this change will not be picked to other branches. it is a breaking change

run test for platform under dev mode

5

Currently, platform tests are running in production mode only, we should test everything under two modes. as we have discovered the issue with running V14+ application on safari 10 under...

``` This message in browser log console may be a potential error: '[2022-02-24T13:55:07.154Z] [WARNING] http://localhost:8080/VAADIN/build/vaadin-3-465efc010957f5308294.cache.js 710:776 "WARNING: Since Vaadin 22, placing the label as a direct child of a \u003Cvaadin-checkbox>...

consider add a parameter for those versions used in different modules ``` com.saucelabs.maven.plugin sauce-connect-plugin 2.1.25 ${sauce.user} ${sauce.sauceAccessKey} ${sauce.options} com.saucelabs ci-sauce 1.151 ```

Add a task to test Vaadin with multi node versions

1

as we promise the vaadin works node XY+, we should test multi node versions.