This updates the test env to test with Node 20 only, pr_check is also updated to use Node 20.
The changes shouldn't affect users in any way, please let me know if you think it might.
There were common async flakes when using testing-library with Node 18, those often surfaced in gh actions / pr_check only and did not reproduce locally unless resources got limited (I can reproduce some flakes in Power Saver mode only, leading me to conclusion, that it's just async being mischievous). Switching to testing with Node 20 only should also allow us to re-enable some tests that got disabled specifically because them running with Node 18 ended up in a time out.
Snyk is now being used for code analysis in favor of Sonarqube. This
commit drops Sonarqube. Schutzbot was only neccessary for running
SonarQube, so it has also been dropped.
For checking wether the api was tempered with, we need separate action,
that just checks the code against the currently pulled spec.
This introduces two subactions for `npx api`.
These are `npx api:generate` and `npx api:pull`.
This bumps a maximum number of opened dependabot PRs as there are currently three open PRs in need of manual revision. Those are blocking any other bumps from being even opened.
The bump should be temporary.
As Travis CI is getting removed from RedHatInsights this should replace it in what we used to use Travis for.
This workflow is triggered on pull requests to main and runs clean install of dependencies, lint check and the unit test suite.
The main motivation of this workflow being separated from the IQE tests is to allow to quickly check if the basic tests pass during development without the need to wait for the IQE tests to finish their run.
This adds the ability to use our Schutzbot Gitlab CI and run Sonarqube
scan there. We have pretty much the exact same thing in weldr-client
repo and use it only for Sonarqube. This could also be used in the
future if there is any need to use our own CI.
The added scan is just informative and is by no means supposed to be
used to gate PRs, there will be just one more link to
check the results in case anyone is interested.
This workflow syncs the main branch with the stage-stable branch.
It also includes a production target which needs to be dispatched
manually. The production target pushes the input ref to both prod-beta
and prod-stable branches.
This results in the main branch always being deployed on stage-beta and
stage-stable, and the prod-beta and prod-stable branches being synced on
release.
