pytest-selective 0.4.0__tar.gz → 0.4.1__tar.gz

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

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

{pytest_selective-0.4.0 → pytest_selective-0.4.1}/CHANGELOG.md

@@ -1,5 +1,12 @@
 # Changelog
 
+## [0.4.1](https://github.com/gigaverse-app/pytest-selective/compare/v0.4.0...v0.4.1) (2026-10-24)
+
+
+### Bug fixes
+
+* **selection:** preserve rerun scope and record planner reasons ([29d1df8](https://github.com/gigaverse-app/pytest-selective/commit/29d1df806816203bad1e7a4a53f38b7e75c1d268))
+
 ## [0.4.0](https://github.com/gigaverse-app/pytest-selective/compare/v0.3.0...v0.4.0) (2026-10-24)
 
 

{pytest_selective-0.4.0 → pytest_selective-0.4.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: pytest-selective
-Version: 0.4.0
+Version: 0.4.1
 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/

{pytest_selective-0.4.0 → pytest_selective-0.4.1}/action.yml

@@ -18,8 +18,8 @@ inputs:
     description: Space-separated complete test roots used if planning cannot prove a narrower scope.
     required: true
   full:
-    description: auto selects on PRs/pushes and runs full on reruns, manual/scheduled/release events or test:full. Override
-      with true or false.
+    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
   extra-files:
     description: Optional newline file containing prior failure canaries or additional changed paths.
@@ -59,6 +59,10 @@ inputs:
       with `head`, so they stay visible after `base` moves to a validated tree. Without it, or without the history, they compare
       against `base`.
     default: ${{ github.event.pull_request.base.sha }}
+  explanation-format:
+    description: 1 preserves the legacy explanation schema; 2 includes the actual planner reasons. Use 2 with a compatible
+      reporter.
+    default: '1'
 outputs:
   base:
     description: The base the selection was made from; `alternate-base` when it selected fewer tests.
@@ -108,3 +112,4 @@ runs:
       dependency-token: ${{ inputs.dependency-token }}
       explanation-artifact: ${{ inputs.explanation-artifact }}
       graph-base: ${{ inputs.graph-base }}
+      explanation-format: ${{ inputs.explanation-format }}

{pytest_selective-0.4.0 → pytest_selective-0.4.1}/actions/plan-lanes/action.yml

@@ -8,7 +8,7 @@ inputs:
     description: Base commit containing the complete change set.
     default: ${{ github.event.pull_request.base.sha || github.event.before }}
   full:
-    description: 'auto selects on PRs/pushes and runs full on reruns, manual/scheduled/release events or test:full. Override with true or false.'
+    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
   artifact-name:
     description: >

{pytest_selective-0.4.0 → pytest_selective-0.4.1}/actions/test-impact/action.yml

@@ -17,7 +17,7 @@ inputs:
     description: Space-separated complete test roots used if planning cannot prove a narrower scope.
     required: true
   full:
-    description: 'auto selects on PRs/pushes and runs full on reruns, manual/scheduled/release events or test:full. Override with true or false.'
+    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
   extra-files:
     description: Optional newline file containing prior failure canaries or additional changed paths.
@@ -60,6 +60,9 @@ inputs:
       its merge base with `head`, so they stay visible after `base` moves to a validated tree.
       Without it, or without the history, they compare against `base`.
     default: ${{ github.event.pull_request.base.sha }}
+  explanation-format:
+    description: '1 preserves the legacy explanation schema; 2 includes the actual planner reasons. Use 2 with a compatible reporter.'
+    default: '1'
 outputs:
   base:
     value: ${{ steps.select.outputs.base }}
@@ -123,6 +126,7 @@ runs:
         # Environment only: the CLI never takes it on argv, and git gets it per process, not in config.
         IMPACT_DEPENDENCY_TOKEN: ${{ inputs.dependency-token }}
         IMPACT_GRAPH_BASE: ${{ inputs.graph-base }}
+        IMPACT_EXPLANATION_FORMAT: ${{ inputs.explanation-format }}
         SHARED_ACTION_PATH: ${{ github.action_path }}
       run: |
         export PYTHONPATH="$SHARED_ACTION_PATH/../../src${PYTHONPATH:+:$PYTHONPATH}"
@@ -139,7 +143,7 @@ runs:
         args=(affected --config "$IMPACT_CONFIG" --base "$IMPACT_BASE" --head "$IMPACT_HEAD"
               --max-shards "$IMPACT_SHARDS" --minimum-files "$IMPACT_MINIMUM" --github-output "$GITHUB_OUTPUT" --output test-impact-report.json
               --durations "$IMPACT_DURATIONS" --shard-seconds "$IMPACT_SHARD_SECONDS"
-              --explanation-output test-impact-explanation.json)
+              --explanation-output test-impact-explanation.json --explanation-format "${IMPACT_EXPLANATION_FORMAT:-1}")
         # A reused workspace must not upload a previous plan's explanation.
         rm -f test-impact-explanation.json
         args+=(--full "$IMPACT_FULL")

{pytest_selective-0.4.0 → pytest_selective-0.4.1}/docs/ci-toolkit.md

@@ -60,8 +60,9 @@ benchmark pairs can be declared with exact run/attempt/head references through
 Never turn the fraction of files or lanes skipped into a measured time saving.
 
 Ordinary label edits no longer launch the CI validation workflows. Add `test:full`
-before the next code update to force full validation, or use an explicit rerun
-or manual dispatch for immediate full execution. Ordinary PRs and main pushes
+before the next code update to force full validation, or use a manual dispatch
+for immediate full execution. A PR/push rerun preserves selection and uses the
+original event payload; adding a label afterward may not change that payload. Ordinary PRs and main pushes
 use dependency selection, including for contract and installed-package tests.
 Unreferenced documentation runs zero tests; explicit full checkpoints and
 failed-planning fallbacks retain complete coverage and required gates.

{pytest_selective-0.4.0 → pytest_selective-0.4.1}/docs/ci.md

@@ -4,6 +4,20 @@ Plan on committed revisions with complete Git history and a known passing base.
 Keep a scheduled full-suite run. Do not drop unresolved failures merely by moving
 the base forward after a failed run.
 
+PR and push reruns preserve the selection policy for the same base, head and
+inputs. Rerunning does not request the full suite. Use `full: 'true'`, a
+`test:full` label present in the event, or a scheduled/manual/release checkpoint
+for full validation. `full: 'false'` overrides event defaults, while missing
+history and operational uncertainty still retain conservative execution.
+
+The planner records its actual reasons once and carries them into its report.
+The CLI explanation format 2 includes `selection_reasons`; `--explanation-format 1`
+omits that field for older strict readers. The public `actions/test-impact@v1`
+action defaults to format 1 for compatibility. A compatible reporter can request
+`explanation-format: '2'`; CI-esta's wrapper does this automatically. Older
+artifacts cannot identify a trigger they never recorded, so readers must say
+that the reason is unavailable rather than infer it from the attempt number.
+
 ## GitHub Actions
 
 This job uses the repository's composite action and runs the plan on the checked-out

{pytest_selective-0.4.0 → pytest_selective-0.4.1}/docs/tutorials/adoption-checklist.md

@@ -12,7 +12,7 @@ services and application installation altogether.
 
 Use this checklist in your adoption PR. Mark each stage **verified**, **deferred**
 or **not applicable**, with a reason. Pair it with the
-[CI-esta adoption checklist](https://github.com/gigaverse-app/ci-esta/blob/6a694957568c81929a2b3021064ad9674516fb7b/docs/tutorials/adoption-checklist.md)
+[CI-esta adoption checklist](https://github.com/gigaverse-app/ci-esta/blob/main/docs/tutorials/adoption-checklist.md)
 for reporting, setup, sharding, history, evidence reuse and security integration.
 Selection remains opt-in; installing the package alone does not narrow pytest.
 

{pytest_selective-0.4.0 → pytest_selective-0.4.1}/docs/tutorials/skip-unrelated-ci.md

@@ -113,7 +113,8 @@ Exercise actual Git commits, not a function that classifies extensions:
 | Missing history or operational uncertainty | Conservative full execution |
 | Invalid configuration | Diagnostic and failed required gate |
 | Ordinary PR or main push containing only unreferenced docs | Zero tests |
-| Manual/release checkpoint, explicit rerun, or `test:full` | Full execution |
+| PR/push rerun | Same selection policy as the first attempt |
+| Manual/release checkpoint or explicit `test:full` request | Full execution |
 
 Select these routing tests through declared dependencies on configuration,
 execution workflows, helpers and the inputs they inspect. Include wheel smoke,
@@ -127,9 +128,9 @@ you can enumerate every job, action, and reusable workflow that affects a lane.
 ## 4. Measure one equivalent pair
 
 Open a README-only probe PR. Save the source SHA, tested merge, run ID and attempt
-of its successful selected run. Add `test:full`, then explicitly rerun the workflow at that revision. A label
-change alone may not trigger CI. The example also forces full execution on
-reruns. Do not change source or workflow settings between the paired runs. Compare successful completed runs;
+of its successful selected run. Use a manual full-checkpoint dispatch at that revision.
+A PR/push rerun alone preserves selection; its event payload may also retain the original labels.
+Do not change source or workflow settings between the paired runs. Compare successful completed runs;
 keep cancelled experiments and observer overhead separate.
 
 Use [CI-esta's critical-path tutorial](https://ci-esta.readthedocs.io/en/latest/docs/tutorials/measure-critical-path/)

pytest_selective-0.4.1/docs/work-in-progress/tickets/rerun-selection-test-plan.md

@@ -0,0 +1,7 @@
+# Rerun selection and explanation reasons
+
+- [x] Real Git file and lane CLI controls: PR/push attempts preserve empty and nonempty selection, including paths with spaces.
+- [x] Explicit full input, label and checkpoint event controls retain full work; uncertain event metadata remains conservative.
+- [x] File explanations carry the resolved planner reasons; format 1 omits the additive field for strict legacy readers.
+- [x] Real action-shell tests preserve operational fallback and explanation replacement.
+- [ ] Hosted platform checks and released-action consumer reruns preserve checks and selective scope.

{pytest_selective-0.4.0 → pytest_selective-0.4.1}/pyproject.toml

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

{pytest_selective-0.4.0 → pytest_selective-0.4.1}/skills/pytest-selective/SKILL.md

@@ -100,7 +100,8 @@ before/after table with evidence. Follow the user's existing PR/merge scope.
 and overlapping runs separately; receipt reuse is a distinct optional decision.
 Keep the [measured impact](https://github.com/gigaverse-app/ci-esta/blob/main/docs/measured-impact.md)
 visible in the report, with linked full/selected controls and a collapsed timeline.
-File-count reduction alone cannot establish time savings. Preserve full reruns
+File-count reduction alone cannot establish time savings. PR/push reruns preserve selection;
+request a full checkpoint explicitly. Preserve explicit full requests
 when removing broad label triggers. Bun projects use their native runner and
 CI-esta's Bun evidence adapter; pytest-selective stays optional for CI-esta.
 The [92.3% README runner-time reduction](https://github.com/gigaverse-app/pytest-selective/blob/main/docs/benchmarks/2026-10-22-routing.md)

{pytest_selective-0.4.0 → pytest_selective-0.4.1}/skills/pytest-selective/references/adoption.md

@@ -83,8 +83,8 @@ python -m pytest_selective.ci --repo . --config .github/test-lanes.json \
 
 For Actions, use `plan-lanes` with full history and expose its `lanes` job output.
 An admitted job runs when its lane is true **or planning failed**. Prefer the
-shared `full: auto` and `base` defaults: reruns, manual/release runs, schedules
-and `test:full` become complete checkpoints; ordinary main pushes use the changed
+shared `full: auto` and `base` defaults: PR/push reruns preserve selection;
+manual/release runs, schedules and `test:full` become complete checkpoints. Ordinary main pushes use the changed
 base/head trees so docs-only merges also execute zero tests. Preserve deliberate
 consumer overrides with explicit `full: 'true'` or `full: 'false'`. Use
 `test_roots_json` when forwarding a file plan; do not split paths on spaces or

{pytest_selective-0.4.0 → pytest_selective-0.4.1}/src/pytest_selective/checkpoint.py

@@ -19,26 +19,37 @@ class _PullRequestEvent(BaseModel):
     pull_request: _PullRequest
 
 
-def full_checkpoint(value: str) -> bool:
+def full_checkpoint_reason(value: str) -> str | None:
     """Resolve auto once at planning; uncertain event metadata requires full work.
 
     Explicit booleans bypass event policy, but never bypass the planners' missing
     history/configuration fallbacks. CLI callers remain selective unless they
     request ``--full`` or ``--full auto``.
     """
-    if value in {"true", "false"}:
-        return value == "true"
+    if value == "true":
+        return "full suite explicitly requested (--full true)"
+    if value == "false":
+        return None
     if value != "auto":
         raise argparse.ArgumentTypeError("full must be auto, true, or false")
     try:
-        if int(os.environ.get("GITHUB_RUN_ATTEMPT", "0")) != 1:
-            return True
         event = os.environ.get("GITHUB_EVENT_NAME", "")
         if event == "push":
-            return False
+            return None
+        if event in {"workflow_dispatch", "workflow_call", "schedule", "release"}:
+            return f"full suite required by {event} checkpoint"
         if event != "pull_request":
-            return True
+            return "full suite fallback: unsupported or missing event metadata"
         payload = _PullRequestEvent.model_validate_json(Path(os.environ["GITHUB_EVENT_PATH"]).read_text())
-        return any(label.name == "test:full" for label in payload.pull_request.labels)
+        return (
+            "full suite requested by test:full label"
+            if any(label.name == "test:full" for label in payload.pull_request.labels)
+            else None
+        )
     except (KeyError, OSError, ValueError, ValidationError):
-        return True
+        return "full suite fallback: pull request event metadata unavailable or invalid"
+
+
+def full_checkpoint(value: str) -> bool:
+    """Compatibility boolean API; the planners retain the reason as well."""
+    return full_checkpoint_reason(value) is not None

{pytest_selective-0.4.0 → pytest_selective-0.4.1}/src/pytest_selective/ci.py

@@ -11,7 +11,7 @@ from typing import Any
 import yaml
 from pydantic import Field, field_validator, model_validator
 
-from pytest_selective.checkpoint import full_checkpoint
+from pytest_selective.checkpoint import full_checkpoint_reason
 from pytest_selective.impact_graph import DependencyDeclarationError, GraphCache, git, matches, within
 from pytest_selective.impact_models import ImpactConfig, ImpactModel
 from pytest_selective.impact_selection import affected
@@ -232,12 +232,16 @@ def main(argv: list[str] | None = None) -> int:
     parser.add_argument("--repo", type=Path, default=Path("."))
     parser.add_argument("--base", required=True)
     parser.add_argument("--head", default="HEAD")
-    parser.add_argument("--full", nargs="?", const=True, default=False, type=full_checkpoint, metavar="auto|true|false")
+    parser.add_argument(
+        "--full", nargs="?", const="true", default="false", type=full_checkpoint_reason, metavar="auto|true|false"
+    )
     parser.add_argument("--github-output", type=Path)
     args = parser.parse_args(argv)
     try:
         config = LaneConfig.model_validate_json(args.config.read_text(encoding="utf-8"))
-        result = plan(args.repo, config, args.base, args.head, full=args.full)
+        result = plan(args.repo, config, args.base, args.head, full=args.full is not None)
+        if args.full is not None:
+            result.reason = args.full
     except (ValueError, OSError, DependencyDeclarationError) as error:
         print(f"Invalid lane configuration/dependency: {error}", file=sys.stderr)
         return 2

{pytest_selective-0.4.0 → pytest_selective-0.4.1}/src/pytest_selective/impact_cli.py

@@ -14,7 +14,7 @@ import time
 from collections.abc import Callable
 from pathlib import Path
 
-from pytest_selective.checkpoint import full_checkpoint
+from pytest_selective.checkpoint import full_checkpoint_reason
 from pytest_selective.impact_audit import audit, load_records, summary
 from pytest_selective.impact_explanation import dependent_tests, explain
 from pytest_selective.impact_graph import (
@@ -161,7 +161,8 @@ def _write_explanation(
         print(f"::warning::Test selection explanation unavailable: {error}", file=sys.stderr)
         return
     args.explanation_output.parent.mkdir(parents=True, exist_ok=True)
-    args.explanation_output.write_text(explanation.model_dump_json(indent=2) + "\n", encoding="utf-8")
+    excluded = {"selection_reasons"} if args.explanation_format == "1" else set()
+    args.explanation_output.write_text(explanation.model_dump_json(indent=2, exclude=excluded) + "\n", encoding="utf-8")
 
 
 def _typecheck_scope(args: argparse.Namespace) -> int:
@@ -291,11 +292,19 @@ def main(argv: list[str] | None = None) -> int:
     parser.add_argument("--output", type=Path)
     # affected: why the selection is this large, for the PR sticky (never changes the selection).
     parser.add_argument("--explanation-output", type=Path)
+    parser.add_argument(
+        "--explanation-format",
+        choices=["1", "2"],
+        default="2",
+        help="format 1 supports legacy readers; format 2 includes planner reasons",
+    )
     # affected: the PR's base, which floor and widening deltas compare against (its merge base).
     parser.add_argument("--graph-base", default="")
     parser.add_argument("--extra-files", type=Path)
     parser.add_argument("--github-output", type=Path)
-    parser.add_argument("--full", nargs="?", const=True, default=False, type=full_checkpoint, metavar="auto|true|false")
+    parser.add_argument(
+        "--full", nargs="?", const="true", default="false", type=full_checkpoint_reason, metavar="auto|true|false"
+    )
     parser.add_argument("--minimum-files", type=int, default=0)
     parser.add_argument("--max-shards", type=int, default=8)
     parser.add_argument("--durations", type=Path, default=Path(".test_durations"))
@@ -316,6 +325,8 @@ def main(argv: list[str] | None = None) -> int:
     # floor-budget: the explanation `affected --explanation-output` wrote for this plan.
     parser.add_argument("--explanation", type=Path, default=Path("test-impact-explanation.json"))
     args = parser.parse_args(argv)
+    full_reason = args.full
+    args.full = full_reason is not None
     args.base = args.base or ("HEAD" if args.working_tree else "HEAD^")
     if args.working_tree and args.command not in {"affected", "warm", "dependencies", "explain", "conftest-impact"}:
         parser.error("--working-tree is supported for affected, warm, dependencies, explain and conftest-impact")
@@ -355,7 +366,7 @@ def main(argv: list[str] | None = None) -> int:
                 snapshot = cache.snapshot(args.repo, args.head, config)
                 report.selected = snapshot.tests
                 report.mode = "full"
-                report.reasons.append("explicit full-suite event/label")
+                report.reasons.append(full_reason)
             if report.selected and len(report.selected) < args.minimum_files:
                 snapshot = cache.snapshot(args.repo, args.head, config)
                 extras = [test for test in snapshot.tests if test not in report.selected]

{pytest_selective-0.4.0 → pytest_selective-0.4.1}/src/pytest_selective/impact_explanation.py

@@ -448,6 +448,7 @@ def explain(
         selected=len(report.selected),
         total=report.total_files,
         forced_full=forced_full,
+        selection_reasons=report.reasons,
         graph_base=graph_before.tree,
         floor_seeds=floor_seeds,
         routes=_routes(union_edges(before, after), report.seeds, report.selected, floor_seeds, reach_after, after),

{pytest_selective-0.4.0 → pytest_selective-0.4.1}/src/pytest_selective/impact_models.py

@@ -458,6 +458,9 @@ class SelectionExplanation(ImpactModel):
     #: The complete suite ran because it was requested (a schedule, a dispatch, coverage, a label),
     #: not because the change reaches every test. Such a run times something other than a PR run.
     forced_full: bool = False
+    #: Planner decisions, including the exact full override, fallback or padding reason.
+    #: Older artifacts omit this field; readers must not guess the missing trigger.
+    selection_reasons: list[str] = Field(default_factory=list)
     #: The tree floor and widening deltas compare against: the PR's merge base, else `base`.
     graph_base: str
     #: Traversal seeds that are startup-floor files: each alone selects nearly every test.

{pytest_selective-0.4.0 → pytest_selective-0.4.1}/tests/test_checkpoint_policy.py

@@ -15,14 +15,16 @@ from tests.testing.git_repo import commit, init, write
     [
         ("pull_request", "1", [], "auto", False),
         ("push", "1", [], "auto", False),
-        ("pull_request", "2", [], "auto", True),
+        ("pull_request", "2", [], "auto", False),
+        ("push", "3", [], "auto", False),
+        ("pull_request", "2", ["test:full"], "auto", True),
         ("pull_request", "1", ["test:full"], "auto", True),
         ("workflow_dispatch", "1", [], "auto", True),
         ("workflow_call", "1", [], "auto", True),
         ("schedule", "1", [], "auto", True),
         ("release", "1", [], "auto", True),
         ("unknown", "1", [], "auto", True),
-        ("pull_request", "invalid", [], "auto", True),
+        ("pull_request", "invalid", [], "auto", False),
         ("pull_request", "1", None, "auto", True),
         ("schedule", "2", [], "false", False),
         ("push", "1", [], "true", True),
@@ -60,7 +62,27 @@ def test_checkpoint_policy_drives_real_selection(tmp_path, monkeypatch, planner,
         str(output),
     ]
     if planner == "files":
-        assert files_main(["affected", *args, "--cache", str(tmp_path / "cache.sqlite3")]) == 0
+        explanation = tmp_path / "explanation.json"
+        assert (
+            files_main(
+                [
+                    "affected",
+                    *args,
+                    "--cache",
+                    str(tmp_path / "cache.sqlite3"),
+                    "--explanation-output",
+                    str(explanation),
+                ]
+            )
+            == 0
+        )
+        reasons = json.loads(explanation.read_text())["selection_reasons"]
+        if policy == "true":
+            assert "full suite explicitly requested (--full true)" in reasons
+        elif policy == "auto" and labels == ["test:full"]:
+            assert "full suite requested by test:full label" in reasons
+        elif policy == "auto" and event in {"schedule", "workflow_dispatch", "workflow_call", "release"}:
+            assert f"full suite required by {event} checkpoint" in reasons
         assert ("mode=full" if full else "mode=none") in output.read_text()
         roots = next(
             line.removeprefix("test_roots_json=")
@@ -73,7 +95,11 @@ def test_checkpoint_policy_drives_real_selection(tmp_path, monkeypatch, planner,
         assert f"tests={str(full).lower()}" in output.read_text()
 
 
-def test_json_output_preserves_selected_paths_with_spaces(tmp_path):
+@pytest.mark.parametrize("attempt", ["1", "2", "7"])
+@pytest.mark.parametrize("explanation_format", ["1", "2"])
+def test_json_output_preserves_selected_paths_with_spaces(tmp_path, monkeypatch, attempt, explanation_format):
+    monkeypatch.setenv("GITHUB_EVENT_NAME", "push")
+    monkeypatch.setenv("GITHUB_RUN_ATTEMPT", attempt)
     init(tmp_path)
     test = "tests/test_with spaces.py"
     write(tmp_path, test, "def test_example(): assert True")
@@ -83,6 +109,7 @@ def test_json_output_preserves_selected_paths_with_spaces(tmp_path):
     commit(tmp_path)
     write(tmp_path, "config.json", json.dumps({"module_roots": ["."], "test_roots": ["tests"]}))
     output = tmp_path / "output"
+    explanation = tmp_path / "explanation.json"
     assert (
         files_main(
             [
@@ -93,6 +120,12 @@ def test_json_output_preserves_selected_paths_with_spaces(tmp_path):
                 str(tmp_path / "config.json"),
                 "--base",
                 base,
+                "--full",
+                "auto",
+                "--explanation-output",
+                str(explanation),
+                "--explanation-format",
+                explanation_format,
                 "--github-output",
                 str(output),
                 "--cache",
@@ -104,3 +137,4 @@ def test_json_output_preserves_selected_paths_with_spaces(tmp_path):
     values = dict(line.split("=", 1) for line in output.read_text().splitlines())
     assert values["mode"] == "scoped"
     assert json.loads(values["test_roots_json"]) == [test]
+    assert ("selection_reasons" in json.loads(explanation.read_text())) == (explanation_format == "2")

{pytest_selective-0.4.0 → pytest_selective-0.4.1}/uv.lock

@@ -907,7 +907,7 @@ wheels = [
 
 [[package]]
 name = "pytest-selective"
-version = "0.4.0"
+version = "0.4.1"
 source = { editable = "." }
 dependencies = [
     { name = "pydantic" },

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

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