Skip to content

ci(js): decide in selector jobs which JavaScript checks run - #1424

Draft
auxesis wants to merge 3 commits into
ci/test-eql-selector-jobfrom
ci/js-selector-jobs
Draft

auxesis wants to merge 3 commits into
ci/test-eql-selector-jobfrom
ci/js-selector-jobs

Conversation

@auxesis

@auxesis auxesis commented Oct 28, 2026

Copy link
Copy Markdown
Contributor

Summary

Five JavaScript and TypeScript workflows used a workflow-level path filter, so they did not start at all on some pull requests. A workflow skipped that way leaves its required checks pending, and GitHub's documentation on required status checks says that blocks a merge.

After this change, each workflow starts on every pull request. A selector job decides which of its jobs run, and a summary job reports the result. Each check runs for the same changes as before.

This pull request is stacked on #1417. Merge that one first.

Changes

  • Workflows: tests.yml, fta-v3.yml, tests-bench.yml, tests-supply-chain.yml, and require-auth-npm-changeset.yml.
  • Selector job: first in each workflow, on ubuntu-latest. It fails when a filter gives no answer on a pull request.
  • Test JS: one filter for all five jobs, every file except docs/plans/. These jobs read most of the repository: Biome checks every file, and run-tests runs the script guards, the typechecks, and every package's tests. It uses dorny's every quantifier, so the !docs/plans/** rule excludes.
  • Other four workflows: one filter each, with the old list.
  • Summary job: last in each workflow. It passes when each needed job passed or was skipped.
  • Push lists: fta-v3.yml, tests-bench.yml, and tests-supply-chain.yml keep a push list. Each matches its selector filter, and the parity test checks that.
  • Audited action: tests-supply-chain.yml is a target of the no-caching lint. That lint allows only audited actions. This adds dorny/paths-filter to AUDITED_ACTIONS in scripts/lint-no-workflow-caching.mjs.
  • Shared test code: the first two commits are the same as in ci(crates): decide in selector jobs which crate checks run #1421.
  • New test: js-selectors.test.mjs pins what each selector decides.
  • Changed tests: the auth changeset test reads its job by id, because the selector is now the first job. It reads the selector filter. The tests.yml filter test reads the selector filter. The parity test loses five entries.

Verification

  • pnpm run test:scripts: 83 files, 1,514 tests passed, 3 skipped.
  • actionlint 1.7.12 with shellcheck 0.11.0 on the five workflows: two SC2129 style findings in tests.yml, at steps this pull request does not change. The base branch has the same two.
  • The dorny audit: I read src/main.ts and package.json of dorny/paths-filter at v3.0.4. On a pull request it lists the changed files through the GitHub REST API. Its dependencies are @actions/core, @actions/exec, @actions/github, and picomatch. None of them caches.
  • Not yet verified: a run on GitHub. This pull request changes each workflow, so each one runs its jobs here.

Related

Review notes

  • Look first at the AUDITED_ACTIONS entry. Adding an action there is a supply-chain decision.
  • impact.yml is not converted. It is an advisory report with no path filter, not a check.
  • In workflow-paths-filter-parity.test.mjs, these pull requests edit neighbouring lines. The second to merge needs a rebase.
  • Merge queue runs select every job. Comparing a queue commit with the entry ahead of it is a separate change.

Test EQL has a selector job, and the other pull request workflows are
getting one each. Each workflow's selector must follow the same rules:
no path filter on pull_request, one dorny/paths-filter step, an output
named after each filter, every job selected on other events, a failure
when a filter gives no answer, `if:` conditions that exclude
pull_request, and a summary job that needs every other job.

workflow-selectors.test.mjs checks those rules for every workflow that
has a selector job, found by scanning. It runs the selector's own
decision script and the summary job's own check.

lib/selector.mjs holds the shared code. It reads a selector job, runs
its script, and works out which jobs a pull request runs from the files
it changes. It reads dorny's `every` quantifier and brace patterns,
which a filter needs to exclude documentation.

The parity test now compares a selector workflow's push paths with the
union of its selector filters, by what each selects from the tracked
files. That replaces Test EQL's written exemption. The dispatch test
holds every selector output open, whatever its name.
Three guards check that a workflow's path filter covers what its jobs
read: the binding build inputs, the auth binding sources, and the
sources the integration suites import. They read `on.push.paths` and
`on.pull_request.paths`. Once a workflow has a selector job, its pull
request list moves into the selector filter of each job, and those
guards would stop checking it.

They now read, per job, the lists that decide whether that job runs:
the workflow's push and pull_request lists, and the selector filter the
job reads. For a workflow without a selector job this is the same two
lists as before. They also check only the jobs that build or load the
binding, not every job in the workflow.
Five JavaScript and TypeScript workflows used a workflow-level path
filter on pull_request. A workflow that a path filter skips leaves its
required checks pending, and GitHub's documentation on required status
checks says that blocks a merge.

Each workflow now runs on every pull request. A `selector` job on a
GitHub-hosted runner decides which jobs run, and fails when a filter
gives no answer. A summary job ends each workflow, and passes when
every needed job passed or was skipped.

Each filter keeps the paths of the filter it replaced, so the checks run
for the same changes as before:

- Test JS: every file except docs/plans/. Its jobs read most of the
  repository, so one filter gates all five. dorny's `every` quantifier
  makes the `!docs/plans/**` rule exclude.
- FTA Complexity, Test Benchmark JS, Test supply chain security and
  Require @cipherstash/auth changeset: one filter each, the old list.

Push lists that remain match the selector filters, which the parity
test checks.

Test supply chain security is a target of the no-caching lint, which
allows only audited actions. dorny/paths-filter is added to
AUDITED_ACTIONS: at the pinned v3.0.4 it lists changed files through
the GitHub REST API, and none of its dependencies caches.

The auth changeset test reads the job by id, because the selector is
now the first job, and reads the selector filter. js-selectors.test.mjs
pins what each selector decides.
@changeset-bot

changeset-bot Bot commented Oct 28, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: fce6df0

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@coderabbitai

coderabbitai Bot commented Oct 28, 2026

Copy link
Copy Markdown
Contributor

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Comment @coderabbitai help to get the list of available commands.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant