diff options
| author | Yuriy Andamasov <yuriy@vyos.io> | 2026-07-12 16:42:21 +0300 |
|---|---|---|
| committer | Yuriy Andamasov <yuriy@vyos.io> | 2026-07-12 16:42:21 +0300 |
| commit | 01a7a7b939af3eba31e776dc07e0e7bee3c47874 (patch) | |
| tree | 00667f3bfc2e0d15af535a1e7f4edde640c238cd /workers/package.json | |
| parent | d353f306c7fb85b76221b2f953abe6b0680e7df3 (diff) | |
| download | vyos-documentation-01a7a7b939af3eba31e776dc07e0e7bee3c47874.tar.gz vyos-documentation-01a7a7b939af3eba31e776dc07e0e7bee3c47874.zip | |
docs-infra: run workers tests on PRs (gap let broken deps land)
apex-deploy.yml's test job only triggered on push to rolling, so no
PR-level check ran the workers/ vitest suite — that's how the vitest
3.2/pool-workers 0.18.4 peer conflict landed on rolling undetected
(two dependabot PRs merged clean since nothing exercised `npm ci` in
workers/ pre-merge).
Add a `pull_request` trigger scoped to `workers/**` so the test job
runs pre-merge. Gate deploy-canary and deploy-production with
`if: github.event_name != 'pull_request'` so PR runs test only —
no canary/production deploys fire on a PR (deploy-production would
also auto-skip via `needs: deploy-canary` once canary skips, but the
explicit `if:` keeps intent visible). Concurrency group now branches
per-event so PR runs queue/cancel independently of the rolling deploy
group instead of colliding with it.
Validated with actionlint + a YAML parse check.
🤖 Generated by [robots](https://vyos.io)
Diffstat (limited to 'workers/package.json')
0 files changed, 0 insertions, 0 deletions
