Bump the production-patch group across 1 directory with 8 updates #1513
Workflow file for this run
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| name: Integrate | |
| permissions: | |
| contents: read | |
| on: | |
| push: | |
| branches: | |
| - main | |
| pull_request: | |
| branches: | |
| - "*" | |
| concurrency: | |
| group: integrate-${{ github.ref }} | |
| jobs: | |
| build: | |
| name: Build | |
| strategy: | |
| matrix: | |
| os: [ubuntu-latest, windows-latest] | |
| # 20 is in Maintenance until April 2026. | |
| # 22 is Active until October 2025, Maintenance until April 2027. | |
| # 24 is Current from April 2025 to October 2025, then Active until October 2026, Maintenance until April 2028. | |
| # 26 will be Current in April 2026. | |
| # https://nodejs.org/en/about/previous-releases | |
| node: [ 20, 22, 24 ] | |
| runs-on: ${{ matrix.os }} | |
| steps: | |
| - uses: actions/checkout@v5 | |
| - uses: actions/setup-node@v6 | |
| with: | |
| node-version: ${{ matrix.node }} | |
| cache: | |
| yarn | |
| # https://docs.github.com/en/actions/security-guides/automatic-token-authentication | |
| - run: > | |
| yarn config set | |
| npmScopes.siteimprove.npmAuthToken | |
| ${{ secrets.GITHUB_TOKEN }} | |
| - run: yarn install --immutable | |
| - name: Install Playwright browsers | |
| # https://playwright.dev/docs/ci-intro | |
| run: yarn workspace @siteimprove/alfa-playwright playwright install | |
| - run: yarn dedupe --check | |
| - run: yarn build --quiet | |
| - name: Run Vitest based tests | |
| # We've seen quite a lot of flakyness on tests, most notably hitting a timeout, and incorrect scraping of the | |
| # immediate redirect pages (alfa-scrape). | |
| # The timeout is not just something we can increase, since "good" runs finish in a few seconds, and the timeout | |
| # is at 1 minute. So it feels like this is not just running close to the limit, but something else going on. | |
| # The alfa-scrape redirect should be investigated at some point. | |
| # In the meantime, we simply allow the test to run a second time to give it a better chance. This does increase | |
| # the time-to-error in case of real problems, but these should hopefully be detected locally by devs before | |
| # creating a PR and running this workflow… | |
| run: yarn test-main || yarn test-main | |
| - run: yarn test-other | |
| - run: yarn validate-structure | |
| - run: yarn extract --quiet | |
| - run: yarn knip |