pytest-selective 1.1.1__tar.gz → 1.2.0__tar.gz

{pytest_selective-1.1.1 → pytest_selective-1.2.0}/.github/workflows/ci.yml

@@ -149,12 +149,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 +187,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.2.0/.github/workflows/dry-lint-audit.yml

@@ -0,0 +1,23 @@
+name: dry-lint audit
+# Weekly, or dispatched after merging a cleanup: dry-lint's own audit workflow sweeps the repository against the
+# accepted backlog and opens or updates one dry-lint/ratchet pull request recording what was cleaned. Its steps ship
+# with dry-lint releases; this file only says when it runs and with which credentials.
+on:
+  schedule:
+    - cron: '23 6 * * 1'
+  workflow_dispatch:
+  # dry-lint.yml calls this file on a manual dispatch, to exercise the audit with the rest of the checks.
+  workflow_call:
+permissions:
+  contents: read
+jobs:
+  audit:
+    uses: gigaverse-app/dry-lint/.github/workflows/audit.yml@v1
+    with:
+      python-version: '3.13'
+      budget-usd: '5'
+      plugins: anthropic==2.4.0
+    secrets:
+      ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}
+      # The organization credential makes the ratchet pull request run ordinary CI.
+      DRY_LINT_RATCHET_TOKEN: ${{ secrets.GV_CI_CROSS_REPO_TOKEN }}

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

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

{pytest_selective-1.1.1 → pytest_selective-1.2.0}/CHANGELOG.md

@@ -1,5 +1,19 @@
 # Changelog
 
+## [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)
+
+
+### Bug fixes
+
+* agent setup round 2, from a second adoption trial ([#114](https://github.com/gigaverse-app/pytest-selective/issues/114)) ([45d4afe](https://github.com/gigaverse-app/pytest-selective/commit/45d4afe76cde9f6093519d97000244c6c06b157d))
+
 ## [1.1.1](https://github.com/gigaverse-app/pytest-selective/compare/v1.1.0...v1.1.1) (2026-11-09)
 
 

{pytest_selective-1.1.1 → pytest_selective-1.2.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.

{pytest_selective-1.1.1 → pytest_selective-1.2.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: pytest-selective
-Version: 1.1.1
+Version: 1.2.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/
@@ -60,9 +60,9 @@ the affected test files, and explains the result. Use it directly as a pytest
 plugin, or plan before collection and service startup with the CLI and CI actions.
 
 Built from the selector used in Gigaverse's backend, AI, and shared Python
-infrastructure. Pin the actions and the package to the same release: `@vX.Y.Z`
-(or its commit SHA) and `pytest-selective==X.Y.Z`. The moving `@v1` tag follows
-the newest release.
+infrastructure. Use the actions at the moving `@v1` tag, which follows the newest
+release, and the package at `pytest-selective>=X.Y.Z,<2`. Where your tooling rejects
+tags, pin both to one release instead: `@<sha> # vX.Y.Z` and `pytest-selective==X.Y.Z`.
 [Provenance and extraction scope](https://github.com/gigaverse-app/pytest-selective/blob/main/PROVENANCE.md).
 
 [Quick tutorial](https://github.com/gigaverse-app/pytest-selective/blob/main/docs/tutorial.md) ·
@@ -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.1 → pytest_selective-1.2.0}/README.md

@@ -29,9 +29,9 @@ the affected test files, and explains the result. Use it directly as a pytest
 plugin, or plan before collection and service startup with the CLI and CI actions.
 
 Built from the selector used in Gigaverse's backend, AI, and shared Python
-infrastructure. Pin the actions and the package to the same release: `@vX.Y.Z`
-(or its commit SHA) and `pytest-selective==X.Y.Z`. The moving `@v1` tag follows
-the newest release.
+infrastructure. Use the actions at the moving `@v1` tag, which follows the newest
+release, and the package at `pytest-selective>=X.Y.Z,<2`. Where your tooling rejects
+tags, pin both to one release instead: `@<sha> # vX.Y.Z` and `pytest-selective==X.Y.Z`.
 [Provenance and extraction scope](https://github.com/gigaverse-app/pytest-selective/blob/main/PROVENANCE.md).
 
 [Quick tutorial](https://github.com/gigaverse-app/pytest-selective/blob/main/docs/tutorial.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.1 → pytest_selective-1.2.0}/actions/plan-lanes/action.yml

@@ -12,8 +12,10 @@ inputs:
     default: auto
   artifact-name:
     description: >
-      Upload the lane plan under this name, where CI-esta's report renders it as
-      the sticky's lane section. Empty skips the upload.
+      Upload the lane plan (test-lanes.json) as an artifact under this name, where
+      CI-esta's report renders it as the sticky's lane section. Give each planner job
+      in one workflow run its own name. Empty skips the upload; planning and the
+      outputs are unchanged.
     default: test-lane-selection
 outputs:
   lanes:

{pytest_selective-1.1.1 → pytest_selective-1.2.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.1 → pytest_selective-1.2.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.1 → pytest_selective-1.2.0}/docs/actions.md

@@ -28,6 +28,10 @@ supported on GitHub.com with runner 2.336.0 or newer. Individual `actions/NAME`
 entry points call the implementations directly and do not require that syntax.
 [GitHub reference documentation](https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax).
 
+`plan-lanes` uploads its plan as the `test-lane-selection` artifact by default. Set
+`artifact-name` to rename it, which a second planner job in the same workflow run needs, or to
+`''` to skip the upload.
+
 ## Action reference
 
 Each link below is the public action's complete input/output contract.

{pytest_selective-1.1.1 → pytest_selective-1.2.0}/docs/ci.md

@@ -253,11 +253,10 @@ job per workflow the required check and run
 gated job to its lanes. It fails unless each prerequisite succeeded or was skipped while
 the planner succeeded and every mapped lane is `false`; a failed planner fails it.
 
-Do not gate a job that a publish or deploy job `needs:` on pull-request-only logic:
-skipping it skips publishing. Keep it running on other events
-(`github.event_name != 'pull_request' || ...`), or plan inside the job with
+Never gate a job that a publish or deploy job `needs:`, directly or transitively:
+skipping it skips publishing. Leave it ungated, or plan inside the job with
 `continue-on-error: true` and admit only its expensive steps, as the `distributions`
-job in this repository's CI does. A branch's first push has no previous commit, so
+job in this repository's CI does. Gate every other job that installs, builds or tests. A branch's first push has no previous commit, so
 `on: push` for every branch runs every lane once per new branch; prefer pull-request
 triggers plus pushes to the default branch.
 The default event policy handles manual/release checkpoints, schedules and

{pytest_selective-1.1.1 → pytest_selective-1.2.0}/docs/configuration.md

@@ -24,9 +24,10 @@ select. The default filenames are `test_*.py`, `*_test.py`, `*_tests.py`, and
 
 ## Review and record collection policy
 
-If your repository has `pyproject.toml`, `pytest.ini`, `tox.ini`, or `setup.cfg`,
-record its committed pytest-policy fingerprints. Even a discovered configuration
-file with no pytest settings can have a fingerprint. This review prevents a new
+If your repository has `pyproject.toml`, `pytest.ini`, a `tox.ini` with a `[pytest]`
+section, or a `setup.cfg` with a `[tool:pytest]` section, record its committed
+pytest-policy fingerprints. A `pyproject.toml` or `pytest.ini` with no pytest settings
+still has a fingerprint, because pytest can still choose it. This review prevents a new
 collection rule from silently invalidating the inventory.
 
 ```bash
@@ -96,7 +97,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
@@ -120,6 +121,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.
@@ -135,7 +179,11 @@ Unsupported checker patterns retain the full-check fallback.
 
 The policy fingerprints cover conventional pytest configuration names, including
 `pytest.toml`, `.pytest.toml`, `.pytest.ini` and nested candidates. Empty candidates
-are included because their presence can change pytest's root and precedence.
+are included because their presence can change pytest's root and precedence. A
+`tox.ini` without `[pytest]` and a `setup.cfg` without `[tool:pytest]` are not: pytest
+skips them. Adding that section later changes the fingerprints and needs a review.
+Releases up to 1.1.1 recorded such a file as the hash of an empty policy; that entry
+is still accepted and needs no refresh.
 Changes require reviewing and refreshing `pytest_policy`; until then planning
 fails safely and the CI action runs the complete configured roots.
 

{pytest_selective-1.1.1 → pytest_selective-1.2.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.2.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.1 → pytest_selective-1.2.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "pytest-selective"
-version = "1.1.1"
+version = "1.2.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.1 → pytest_selective-1.2.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.1.1 → pytest_selective-1.2.0}/scripts/measure_ci_runs.py

@@ -5,6 +5,10 @@ head. A side may hold several workflow runs (for example CI and Docs triggered b
 push): runner-seconds add up and elapsed runs from the first run's creation to the last job's
 completion. `--expected-failure JOB` accepts that job's deliberate failure (a probe) as executed
 work instead of rejecting the run; any other failed, cancelled or unfinished job still does.
+
+The sides may come from different events. A `pull_request` run records the branch head as its
+`head_sha` (although it checks out the merge commit), so a `workflow_dispatch` or `push` run on
+that branch is the same head: the usual full control beside a selected pull-request run.
 """
 
 import argparse

pytest_selective-1.2.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:]]))