one only calling npm run check, which can just reveal some unrelated formatting changes missing. Those findings still have to be fixed, but in most cases have no consequences in regards to if the example workflow runs are all valid or not.
one calling npm run build and checking if there are no updates = all updates in the ./dist folder are committed... If this job fails, then all the examples runs have to be taken with a grain of salt, as they run agains an outdated ./dist folder, thus being invalid!
This information was previously not visible / masked as mostly npm run check failed and prevented npm run build from running ... it was then unclear, if that has consequences to the ncc compiled stuff in ./dist or not.
Also switching npm install to npm ci to install the exact versions from package-lock.json (managed by dependabot). This is faster, more secure and 100% predictable. Thus removing the cron triggers as those won't find anything new.
This splits the lint flow into two jobs:
npm run check
, which can just reveal some unrelated formatting changes missing. Those findings still have to be fixed, but in most cases have no consequences in regards to if the example workflow runs are all valid or not.npm run build
and checking if there are no updates = all updates in the ./dist folder are committed... If this job fails, then all the examples runs have to be taken with a grain of salt, as they run agains an outdated ./dist folder, thus being invalid!This information was previously not visible / masked as mostly
npm run check
failed and preventednpm run build
from running ... it was then unclear, if that has consequences to the ncc compiled stuff in ./dist or not.Also switching
npm install
tonpm ci
to install the exact versions from package-lock.json (managed by dependabot). This is faster, more secure and 100% predictable. Thus removing the cron triggers as those won't find anything new.