pytest-selective 1.1.2__tar.gz → 1.3.0__tar.gz

{pytest_selective-1.1.2 → pytest_selective-1.3.0}/.github/workflows/ci.yml

@@ -6,8 +6,6 @@ on:
     types: [opened, synchronize, reopened]
   workflow_dispatch:
   workflow_call:
-  schedule:
-    - cron: '13 3 * * 1'
 permissions:
   contents: read
 concurrency:
@@ -149,12 +147,13 @@ jobs:
       - name: Record coverage runtime
         run: uv run --locked python -m coverage --version
       - name: Execute the shared affected-file plan
-        run: uv run --locked python scripts/run_ci_tests.py -q -n 4 --durations=20 --junitxml=test-timings.xml
+        run: uv run --locked pytest-selective execute-plan -- -q -n 4 --dist=worksteal --durations=20 --junitxml=test-timings.xml
         env:
           CI_PLANNER_RESULT: ${{ needs.select-tests.result }}
           CI_TEST_MODE: ${{ needs.select-tests.outputs.mode }}
           CI_TEST_FILES: ${{ needs.select-tests.outputs.files }}
-          CI_COVERAGE: 'true'
+          # Full coverage on each OS; 3.11 retains the same compatibility tests without duplicate instrumentation.
+          CI_COVERAGE: ${{ matrix.python == '3.14' }}
           # Keep temporary Git repositories beside the checkout on the work disk.
           TMP: ${{ runner.temp }}
           TEMP: ${{ runner.temp }}
@@ -186,7 +185,7 @@ jobs:
           python-version: '3.11'
       - run: uv pip install 'pytest==8.0.0'
       - name: Execute the same file plan on minimum pytest
-        run: uv run --no-sync python scripts/run_ci_tests.py -q -n 4 --durations=20
+        run: uv run --no-sync pytest-selective execute-plan -- -q -n 4 --dist=worksteal --durations=20
         env:
           CI_PLANNER_RESULT: ${{ needs.select-tests.result }}
           CI_TEST_MODE: ${{ needs.select-tests.outputs.mode }}

{pytest_selective-1.1.2 → pytest_selective-1.3.0}/.github/workflows/pr-title.yml

@@ -2,7 +2,8 @@ name: PR title
 
 # Squash merges use this checked title as the Conventional Commit header.
 on:
-  pull_request_target:
+  # Metadata reads need no privileged target event or repository secrets.
+  pull_request:
     types: [opened, edited, synchronize, reopened, ready_for_review]
 
 permissions:

{pytest_selective-1.1.2 → pytest_selective-1.3.0}/.github/workflows/public-actions.yml

@@ -4,8 +4,6 @@ on:
   push:
     branches: [main]
   workflow_dispatch:
-  schedule:
-    - cron: '33 3 * * 1'
 permissions:
   contents: read
 jobs:

pytest_selective-1.3.0/.github/workflows/weekly-checkpoint.yml

@@ -0,0 +1,21 @@
+name: Weekly full checkpoint
+'on':
+  schedule:
+  - cron: 13 3 * * 1
+  workflow_dispatch: null
+permissions:
+  contents: read
+  actions: write
+concurrency:
+  group: weekly-full-checkpoint
+  cancel-in-progress: false
+jobs:
+  dispatch:
+    runs-on: ubuntu-latest
+    timeout-minutes: 5
+    steps:
+    - uses: gigaverse-app/ci-esta/actions/weekly-checkpoint@v1
+      with:
+        workflows: '["ci.yml", "public-actions.yml"]'
+        ref: ''
+        workflow-inputs: '{}'

pytest_selective-1.3.0/.release-please-manifest.json

@@ -0,0 +1,3 @@
+{
+  ".": "1.3.0"
+}

{pytest_selective-1.1.2 → pytest_selective-1.3.0}/CHANGELOG.md

@@ -1,5 +1,26 @@
 # Changelog
 
+## [1.3.0](https://github.com/gigaverse-app/pytest-selective/compare/v1.2.0...v1.3.0) (2026-11-09)
+
+
+### Features
+
+* **audit:** show how many tests each written declaration selects ([#124](https://github.com/gigaverse-app/pytest-selective/issues/124)) ([b660301](https://github.com/gigaverse-app/pytest-selective/commit/b660301be82aefb04fdc79202dc83067c28d7eb1))
+
+
+### Bug fixes
+
+* agent setup round 3, from a third adoption trial ([#127](https://github.com/gigaverse-app/pytest-selective/issues/127)) ([a82bea9](https://github.com/gigaverse-app/pytest-selective/commit/a82bea9f607abcb3ed68009571202ad8b7726c7e))
+* **selection:** keep every module a pytest11 entry-point name maps to ([#122](https://github.com/gigaverse-app/pytest-selective/issues/122)) ([acb6649](https://github.com/gigaverse-app/pytest-selective/commit/acb66492c6440621387e0506c1d0071a5a48979c))
+* **selection:** plan a pull request against its merge commit's actual base ([#119](https://github.com/gigaverse-app/pytest-selective/issues/119)) ([276cec8](https://github.com/gigaverse-app/pytest-selective/commit/276cec84f65c889a1820fd5a001a3a4aca8b7e0d))
+
+## [1.2.0](https://github.com/gigaverse-app/pytest-selective/compare/v1.1.2...v1.2.0) (2026-11-09)
+
+
+### Features
+
+* **ci:** share plan execution and reduce matrix instrumentation ([1fe0f36](https://github.com/gigaverse-app/pytest-selective/commit/1fe0f36463d4354a99ea3f45406825fa728a12c2))
+
 ## [1.1.2](https://github.com/gigaverse-app/pytest-selective/compare/v1.1.1...v1.1.2) (2026-11-09)
 
 

{pytest_selective-1.1.2 → pytest_selective-1.3.0}/CONTRIBUTING.md

@@ -79,7 +79,9 @@ split indexes and linked worktrees without modifying the user's index or HEAD.
 CI tests Python 3.11 and 3.14 on Linux, Windows, and macOS. A separate job checks
 pytest 8.0.0 on Python 3.11, the plugin's lower bound. It also checks hooks, builds both distribution
 formats, validates PyPI metadata, and installs each distribution in an isolated
-environment on both Python versions. Evidence artifacts carry coverage and tutorial output on every platform and Python version.
+environment on both Python versions. JUnit retains results and timings on every platform and Python version.
+Full runs collect coverage on Python 3.14 on all three operating systems; Python 3.11 runs the same compatibility
+tests without a duplicate instrumentation pass. Each runner uses four work-stealing workers.
 
 Use `uv lock --upgrade-package NAME` for a targeted dependency update and run the
 affected checks. Dependabot proposes weekly uv and GitHub Actions updates.
@@ -116,8 +118,8 @@ File planning derives its graph from that same lane config and merges its declar
 global execution inputs with the graph's environment inputs. Declare subprocess
 and non-import dependencies at their readers. Full plans collect whole-suite
 coverage; scoped plans produce JUnit timing evidence without presenting partial
-coverage as a whole-suite result. The small execution wrapper only consumes the
-public action's JSON file list: it does not implement another selector.
+coverage as a whole-suite result. The public [shared-plan executor](docs/shared-plan-execution.md)
+consumes the action's JSON file list without implementing another selector.
 The outer pytest process disables the selective plugin to avoid a second planner
 and a hidden dependency of every test on plugin startup. Plugin integration tests
 still load it normally in subprocesses and declare that dependency explicitly.
@@ -197,14 +199,19 @@ history or failed planning must execute the full affected lanes and fail the
 required planning gate. Ordinary PRs and pushes use selection; manual/release/scheduled/full overrides
 remain complete checkpoints.
 
-CI and public-action smoke run full checkpoints every Monday. Ordinary runs keep
+The **Weekly full checkpoint** workflow dispatches CI and public-action smoke
+every Monday using [CI-esta's shared action](https://github.com/gigaverse-app/ci-esta/blob/main/docs/weekly-checkpoints.md).
+Its small wrapper is generated by `ci-esta checkpoint init`; the source guide
+documents schedule, workflow, ref and input overrides. Ordinary runs keep
 the shared affected-file plan across all six OS/Python combinations and minimum
 pytest. `tests/test_tutorial.py` owns the end-to-end tutorial execution and follows
 that plan; there is no second tutorial invocation in each matrix job. JUnit retains
 its test result and timing, and full plans also upload whole-suite coverage.
 
-To run a complete checkpoint after a CI change, select **CI** in GitHub Actions
-and choose **Run workflow**. Retrying an ordinary PR run preserves its selection;
+To run both complete checkpoints after a CI change, select **Weekly full checkpoint**
+in GitHub Actions and choose **Run workflow**, then inspect the dispatched CI and
+public-action results. A green dispatcher means both requests were accepted.
+You can also dispatch either target directly. Retrying an ordinary PR run preserves its selection;
 use the manual checkpoint when you need full-suite coverage evidence.
 
 ## Duplication

{pytest_selective-1.1.2 → pytest_selective-1.3.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: pytest-selective
-Version: 1.1.2
+Version: 1.3.0
 Summary: Explainable Python test impact analysis: select affected pytest files from Git changes
 Project-URL: Homepage, https://github.com/gigaverse-app/pytest-selective
 Project-URL: Documentation, https://pytest-selective.readthedocs.io/en/latest/
@@ -237,7 +237,7 @@ skip pytest, because invoking pytest without paths runs the whole suite.
 | --- | --- |
 | A transitive dependency | Import chains and package initialization |
 | A deleted or renamed module | Dependencies in both the base and head trees |
-| Fixtures or startup code | Ancestor conftests, plugins named by `-p` in `addopts`, and configured global modules |
+| Fixtures or startup code | Ancestor conftests, plugins named by `-p` in `addopts`, the project's own `pytest11` entry points, and configured global modules |
 | Templates, schemas, or data files | [Reader-owned declarations and YAML sidecars](docs/tutorials/sidecar-dependencies.md) |
 | A surprisingly large selection | Dependency paths, startup-floor and blast-radius explanations |
 | A large CI suite | Cached parsing, graph reuse, and duration-based shard planning |

{pytest_selective-1.1.2 → pytest_selective-1.3.0}/README.md

@@ -206,7 +206,7 @@ skip pytest, because invoking pytest without paths runs the whole suite.
 | --- | --- |
 | A transitive dependency | Import chains and package initialization |
 | A deleted or renamed module | Dependencies in both the base and head trees |
-| Fixtures or startup code | Ancestor conftests, plugins named by `-p` in `addopts`, and configured global modules |
+| Fixtures or startup code | Ancestor conftests, plugins named by `-p` in `addopts`, the project's own `pytest11` entry points, and configured global modules |
 | Templates, schemas, or data files | [Reader-owned declarations and YAML sidecars](docs/tutorials/sidecar-dependencies.md) |
 | A surprisingly large selection | Dependency paths, startup-floor and blast-radius explanations |
 | A large CI suite | Cached parsing, graph reuse, and duration-based shard planning |

{pytest_selective-1.1.2 → pytest_selective-1.3.0}/action.yml

@@ -14,6 +14,11 @@ inputs:
   head:
     description: Exact checked-out commit.
     default: HEAD
+  pr-head:
+    description: The pull request's head. When the checkout is GitHub's merge of it (refs/pull/N/merge), changes are measured
+      from that merge's base-branch parent, so commits that landed on the base branch after `base` are not counted as the
+      PR's. Empty (any other event) keeps `base`.
+    default: ${{ github.event.pull_request.head.sha }}
   full-roots:
     description: Space-separated complete test roots used if planning cannot prove a narrower scope.
     required: true
@@ -100,6 +105,7 @@ runs:
       config: ${{ inputs.config }}
       base: ${{ inputs.base }}
       head: ${{ inputs.head }}
+      pr-head: ${{ inputs.pr-head }}
       full-roots: ${{ inputs.full-roots }}
       full: ${{ inputs.full }}
       extra-files: ${{ inputs.extra-files }}

{pytest_selective-1.1.2 → pytest_selective-1.3.0}/actions/plan-lanes/action.yml

@@ -7,6 +7,12 @@ inputs:
   base:
     description: Base commit containing the complete change set.
     default: ${{ github.event.pull_request.base.sha || github.event.before }}
+  pr-head:
+    description: >-
+      The pull request's head. When the checkout is GitHub's merge of it (refs/pull/N/merge), changes are measured from
+      that merge's base-branch parent, so commits that landed on the base branch after `base` are not counted as the PR's.
+      Empty (any other event) keeps `base`.
+    default: ${{ github.event.pull_request.head.sha }}
   full:
     description: 'auto preserves selection on PR/push reruns and runs full for manual/scheduled/release checkpoints or test:full. Override with true or false.'
     default: auto
@@ -40,10 +46,12 @@ runs:
         SELECTIVE_CONFIG: ${{ inputs.config }}
         SELECTIVE_BASE: ${{ inputs.base }}
         SELECTIVE_FULL: ${{ inputs.full }}
+        SELECTIVE_PR_HEAD: ${{ inputs.pr-head }}
       run: |
         export PYTHONPATH="$SELECTIVE_ACTION/../../src${PYTHONPATH:+:$PYTHONPATH}"
         args=(--config "$SELECTIVE_CONFIG" --base "$SELECTIVE_BASE" --github-output "$GITHUB_OUTPUT")
         args+=(--full "$SELECTIVE_FULL")
+        if [ -n "$SELECTIVE_PR_HEAD" ]; then args+=(--pr-head "$SELECTIVE_PR_HEAD"); fi
         uv run --no-project --python 3.14 --with pydantic==2.13.4 --with pyyaml==6.0.3 \
           python -m pytest_selective.ci "${args[@]}" | tee test-lanes.json
         {

{pytest_selective-1.1.2 → pytest_selective-1.3.0}/actions/test-impact/action.yml

@@ -13,6 +13,12 @@ inputs:
   head:
     description: Exact checked-out commit.
     default: HEAD
+  pr-head:
+    description: >-
+      The pull request's head. When the checkout is GitHub's merge of it (refs/pull/N/merge), changes are measured from
+      that merge's base-branch parent, so commits that landed on the base branch after `base` are not counted as the PR's.
+      Empty (any other event) keeps `base`.
+    default: ${{ github.event.pull_request.head.sha }}
   full-roots:
     description: Space-separated complete test roots used if planning cannot prove a narrower scope.
     required: true
@@ -114,6 +120,7 @@ runs:
         IMPACT_CONFIG: ${{ inputs.config }}
         IMPACT_BASE: ${{ inputs.base }}
         IMPACT_HEAD: ${{ inputs.head }}
+        IMPACT_PR_HEAD: ${{ inputs.pr-head }}
         IMPACT_FULL: ${{ inputs.full }}
         IMPACT_EXTRA: ${{ inputs.extra-files }}
         IMPACT_ALTERNATE_BASE: ${{ inputs.alternate-base }}
@@ -147,6 +154,7 @@ runs:
         # A reused workspace must not upload a previous plan's explanation.
         rm -f test-impact-explanation.json
         args+=(--full "$IMPACT_FULL")
+        if [ -n "${IMPACT_PR_HEAD:-}" ]; then args+=(--pr-head "$IMPACT_PR_HEAD"); fi
         if [ -n "$IMPACT_EXTRA" ]; then args+=(--extra-files "$IMPACT_EXTRA"); fi
         if [ -n "${IMPACT_GRAPH_BASE:-}" ]; then args+=(--graph-base "$IMPACT_GRAPH_BASE"); fi
         # Optional: an unfetchable alternate only forgoes a smaller selection.

{pytest_selective-1.1.2 → pytest_selective-1.3.0}/contracts/selection/conftest.py

@@ -305,7 +305,8 @@ class RepositoryDriver(SelectionDriver):
         changed = set(git_text(self.root, "diff", "--name-only", "--no-renames", base, self.head).splitlines())
         tests = self._tests(self.head)
         at_head = self._runtime(self.head, tests)
-        at_base = self._runtime(base, [test for test in tests if test in set(self._tests(base))])
+        base_tests = set(self._tests(base))
+        at_base = self._runtime(base, [test for test in tests if test in base_tests])
         needed = {test for test in tests if (at_head[test] | at_base.get(test, frozenset())) & changed}
         return {NAMES[test] for test in needed} - set(selection["selected"])
 

{pytest_selective-1.1.2 → pytest_selective-1.3.0}/contracts/selection/runtime_deps.py

@@ -9,12 +9,16 @@ Modules and sys.path are restored between test files, so each file's dependencie
 import json
 import os
 import sys
+from functools import cache
 from pathlib import Path
 
 import pytest
 
 
+@cache
 def _under(root: Path, path: str | None) -> str | None:
+    # Each process inspects one immutable exported tree. Cache path resolution,
+    # never the per-test import/open observations, which remain isolated below.
     if not path:
         return None
     try:

{pytest_selective-1.1.2 → pytest_selective-1.3.0}/docs/ci.md

@@ -64,6 +64,14 @@ controls the test interpreter. `full-roots` must contain the complete roots, not
 the previous selection. `base` defaults to the PR base or the push's previous
 commit. Override it only when you have validated a different comparison base.
 
+On a pull request, GitHub checks out a merge of the PR head into the base
+branch's current tip, which can be newer than the PR's recorded base. Both
+actions pass the PR head (`pr-head`) so the planner measures changes from that
+merge's base-branch parent. Commits that landed on the base branch after the PR
+was opened, such as a release's version bump, are then not counted as the PR's
+own. A shallow checkout or any other event keeps `base`. Check out with
+`fetch-depth: 0` to get the narrower plan.
+
 Both file and lane actions default to `full: auto`:
 
 | Trigger | Default |

{pytest_selective-1.1.2 → pytest_selective-1.3.0}/docs/configuration.md

@@ -22,6 +22,11 @@ select. The default filenames are `test_*.py`, `*_test.py`, `*_tests.py`, and
 `tests.py`; configure
 `test_patterns` for a different collection policy.
 
+Every `--config` (`affected`, `explain`, `fingerprints`, `audit`, `run` and the rest) also accepts a
+[lane config](ci.md) such as `.github/test-lanes.json`: it uses the lane config's `graph`, with its
+top-level `global_inputs` when declared. Pass the lane config itself rather than a copy of its graph,
+so a later `graph.pytest_policy` refresh is always the one in use.
+
 ## Review and record collection policy
 
 If your repository has `pyproject.toml`, `pytest.ini`, a `tox.ini` with a `[pytest]`
@@ -61,6 +66,9 @@ fixture example, directory manifests, dependency comments, and dynamic Python in
 
 A read that names a tracked file by literal path, such as `open("data/prices.json")` or
 `(Path(__file__).parent / "prices.json").read_text()`, is followed automatically as a content read.
+A string that only names a tracked file, such as a routing test's `("bench.py", ...)` row, adds no
+edge: a dotted string is followed as a possible module name (a patch target, a plugin) only when it
+names no tracked file, from the repository root or beside its reader.
 For a path that is computed, or built from several parts, add a reader-owned comment:
 
 ```python
@@ -97,7 +105,7 @@ patterns to your actual inventory. Central-rule reader patterns use shell-style
 matching: here `*` also covers nested paths under `tests/`. Common lockfiles, dependency manifests and pytest configuration already belong
 to the default `global_inputs`. Keep those defaults unless you have reviewed a
 narrower environment contract; these reader-specific rules are for additional
-inputs. Other non-Python files are not automatically global inputs. Plugins named by `-p NAME` in a pytest configuration's `addopts` are global modules automatically; plugins passed only on the command line or in `PYTEST_ADDOPTS` are not visible to the planner. Use `global_modules` for those and other modules loaded by every test and
+inputs. Other non-Python files are not automatically global inputs. Plugins named by `-p NAME` in a pytest configuration's `addopts` are global modules automatically, and so are the project's own `pytest11` entry points (`[project.entry-points.pytest11]` or `[tool.poetry.plugins.pytest11]` in any tracked `pyproject.toml`) whose module is a tracked file. An entry point stays global unless every pytest configuration disables it, with `-p no:NAME` (`NAME` is the entry point's name) or `--disable-plugin-autoload` in `addopts`. Plugins passed only on the command line or in `PYTEST_ADDOPTS`, and `PYTEST_DISABLE_PLUGIN_AUTOLOAD`, are not visible to the planner. Use `global_modules` for those and other modules loaded by every test and
 `always_run` for explicit canary test paths. Retain full-suite checkpoints.
 
 ## Explain and audit
@@ -121,6 +129,49 @@ pytest-selective audit --config .github/test-impact.json --records impact-audit
 Audit results cover executed paths, not every possible execution. Declare missing
 edges at their readers. See [evidence and limitations](evidence.md).
 
+### Write the missing declarations
+
+`audit --write-declarations` writes a rule for every undeclared read into the
+reading test's sidecar, `<test>.gv-dependency.yaml`, creating it or appending to
+the one it already has:
+
+```bash
+pytest-selective audit --config .github/test-impact.json --records impact-audit   --write-declarations
+pytest-selective audit --config .github/test-impact.json --records impact-audit   --working-tree   # confirms nothing is left before you commit
+```
+
+```yaml
+dependencies:
+  - inputs:
+      - "//examples/backgrounds/**"
+      - "//examples/gold.toml"
+    kind: content
+    reason: "Read at runtime; recorded by pytest-selective audit --write-declarations."
+  - inputs:
+      - "//scripts/replay_coverage.py"
+    kind: import
+    reason: "Loaded or run outside the test's imports; recorded by pytest-selective audit --write-declarations."
+```
+
+- A Python input becomes an `import` rule: a test that runs a script in a
+  subprocess also depends on what the script imports. Any other input becomes a
+  `content` rule. Review the kind where the test only reads Python as text.
+- Several reads in one directory become `<directory>/**` only when the test read
+  every tracked file under it, so the glob claims nothing the run did not see.
+  It also covers files added there later.
+- Every pattern must match a tracked file at the audited revision. A path the
+  pattern language cannot express (for example one containing `[`) is printed as
+  `not declared` and the command exits 2.
+- Appending keeps an existing sidecar's text and comments. When the result would
+  not parse to exactly the old rules plus the new ones, the file is left alone
+  and the rules are printed for you to add by hand.
+
+The command prints each sidecar and pattern it wrote and exits 0 when every
+undeclared read was declared. The files are in the working tree, so the plain
+audit (which reads `--head`) still reports them until you commit; use
+`--working-tree` to check first. Prefer a hand-written comment or directory
+manifest where it reads better; the writer only removes the transcription step.
+
 Audit discovery uses the requested repository even when a calling Git hook exports
 location variables for another checkout. It shares repository isolation with the
 planner and expansion guard.

{pytest_selective-1.1.2 → pytest_selective-1.3.0}/docs/selection-health.md

@@ -30,7 +30,8 @@ uv run pytest-selective audit --config .github/test-impact.json --records impact
 The recorder observes real file reads in the tests you execute. The audit can
 expose a JSON fixture, template or schema that the graph did not declare. Add an
 edge at the reader using a dependency comment or YAML sidecar, then recheck the
-route. [Work through the sidecar tutorial](tutorials/sidecar-dependencies.md), or consult
+route. `audit --write-declarations` writes those sidecars for you; see
+[write the missing declarations](configuration.md#write-the-missing-declarations). [Work through the sidecar tutorial](tutorials/sidecar-dependencies.md), or consult
 [declaration syntax](configuration.md#declare-inputs-that-imports-cannot-describe).
 The audit covers observed paths; keep representative full runs for paths it has
 not seen, and explicitly model dynamic imports and external inputs.

pytest_selective-1.3.0/docs/shared-plan-execution.md

@@ -0,0 +1,43 @@
+# Plan once, execute across compatibility lanes
+
+Use `pytest-selective execute-plan` to run a file plan emitted by the public
+test-impact action. Every matrix job consumes the same plan; it does not need
+Git history or a second dependency analysis.
+
+```yaml
+- run: uv run --locked pytest-selective execute-plan -- -q -n 4 --dist=worksteal
+  env:
+    CI_PLANNER_RESULT: ${{ needs.plan.result }}
+    CI_TEST_MODE: ${{ needs.plan.outputs.mode }}
+    CI_TEST_FILES: ${{ needs.plan.outputs.files }}
+    CI_COVERAGE: 'true'
+```
+
+`files` must be the action's `test_roots_json` output. A successful `none` plan
+does not start pytest. Failed planning, malformed JSON, unknown modes or an
+empty scoped selection execute the complete roots. Roots default to `tests`;
+override with `--full-roots tests/unit tests/integration -- ...`. Paths with
+spaces remain single arguments, and pytest receives its normal exit status.
+
+`CI_COVERAGE=true` adds `--cov --cov-report=term-missing --cov-report=xml` only
+for full execution. The environment must have pytest-cov installed. Keep
+coverage thresholds in your project configuration; do not enforce a full-suite
+threshold on selected files. The outer execution disables the selective plugin
+because planning already happened. Integration tests can still load it explicitly.
+
+When lane and file selection share a graph, derive the file config:
+
+```sh
+pytest-selective file-config --lanes .github/test-lanes.json --output /tmp/test-impact.json
+```
+
+This combines the graph's global inputs with the lane config's explicit global
+inputs. Declare `global_inputs` before using it. Lane-specific `inputs` remain
+lane admission rules; they do not automatically make every test file affected.
+Declare non-import dependencies in the graph as usual.
+
+pytest-selective's own CI uses four work-stealing workers on each existing
+runner. Its full checkpoints retain all Python 3.11 and 3.14 compatibility tests
+on Linux, Windows and macOS. Coverage runs on Python 3.14 on all three systems,
+avoiding a second instrumentation pass on Python 3.11. The minimum-pytest lane,
+Quint contract and installed-distribution smoke remain independent checks.

{pytest_selective-1.1.2 → pytest_selective-1.3.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "pytest-selective"
-version = "1.1.2"
+version = "1.3.0"
 description = "Explainable Python test impact analysis: select affected pytest files from Git changes"
 readme = "README.md"
 requires-python = ">=3.11"

{pytest_selective-1.1.2 → pytest_selective-1.3.0}/scripts/ci_file_config.py

@@ -4,15 +4,8 @@ import sys
 from pathlib import Path
 
 from pytest_selective.ci import LaneConfig
-from pytest_selective.impact_models import ImpactConfig
 
-
-def file_config(lanes: LaneConfig) -> ImpactConfig:
-    if lanes.global_inputs is None:
-        raise ValueError("This repository must declare its shared CI execution inputs")
-    return lanes.graph.model_copy(
-        update={"global_inputs": sorted(set(lanes.graph.global_inputs) | set(lanes.global_inputs))}
-    )
+file_config = LaneConfig.file_config
 
 
 if __name__ == "__main__":

pytest_selective-1.3.0/scripts/run_ci_tests.py

@@ -0,0 +1,8 @@
+"""Compatibility entry point for the public shared-plan executor."""
+
+import sys
+
+from pytest_selective.execution import main
+
+if __name__ == "__main__":
+    raise SystemExit(main(["--", *sys.argv[1:]]))