log-foundry 0.10.2.dev86__tar.gz → 0.10.2.dev87__tar.gz

{log_foundry-0.10.2.dev86 → log_foundry-0.10.2.dev87}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: log-foundry
-Version: 0.10.2.dev86
+Version: 0.10.2.dev87
 Summary: Generate logs for your console and JSON events for downstream consumption.
 License-Expression: MIT
 License-File: LICENSE
@@ -1308,15 +1308,24 @@ Deeper design docs live in [`docs/`](docs/) — start with [`docs/architecture.m
 
 ### Continuous integration
 
-Every pull request and every push to `main` runs the same set of checks:
+Every pull request runs the checks below. A check whose verdict cannot change on the tree in
+front of it is path-filtered rather than run to the same answer twice, so the *When* column is
+part of the contract:
 
-| Check | Does | Fails the build |
-|---|---|---|
-| [`ci.yml`](.github/workflows/ci.yml) | ruff → mypy → pytest, on 3.12 **and** 3.13 | yes |
-| [`spec-lint.yml`](.github/workflows/spec-lint.yml) | lints the design specs under `docs/specs/` | yes |
-| [`dependency-review.yml`](.github/workflows/dependency-review.yml) | fails a PR that *introduces* a dependency with a known advisory (`moderate`+) | yes |
-| [`zizmor.yml`](.github/workflows/zizmor.yml) | static analysis of the workflow files themselves | no — reports to code scanning |
-| CodeQL | `python` + `actions`, `extended` query suite; also weekly | no — reports to code scanning |
+| Check | Does | When | Fails the build |
+|---|---|---|---|
+| [`ci.yml`](.github/workflows/ci.yml) | ruff → mypy → pytest, on 3.12 **and** 3.13 | every PR | yes |
+| [`spec-lint.yml`](.github/workflows/spec-lint.yml) | lints the design specs under `docs/specs/` | specs touched | yes |
+| [`dependency-review.yml`](.github/workflows/dependency-review.yml) | fails a PR that *introduces* a dependency with a known advisory (`moderate`+) | every PR | yes |
+| [`zizmor.yml`](.github/workflows/zizmor.yml) | static analysis of the workflow files themselves | workflow, action, dependabot or zizmor config touched; also weekly | no — reports to code scanning |
+| CodeQL | `python` + `actions`, `extended` query suite; also weekly | every PR | no — reports to code scanning |
+
+On a push to `main` the full `ci.yml` matrix still runs, but as the first job of
+[`release.yml`](.github/workflows/release.yml), which `uses:` this same workflow before it is
+allowed to publish — so on main the checks are listed under the *Release* workflow, named
+`test / test (py3.12)` and `test / test (py3.13)`. `ci.yml` deliberately carries no `push`
+trigger of its own; it had one, and the result was that every merge ran the identical matrix
+twice. A `v*` tag is gated the same way, by that same reusable call.
 
 CodeQL runs as GitHub's **default setup** — a repository setting, not a workflow file, which is
 why there is no `codeql.yml` here (adding one would disable the default setup and silently stop

{log_foundry-0.10.2.dev86 → log_foundry-0.10.2.dev87}/README.md

@@ -1272,15 +1272,24 @@ Deeper design docs live in [`docs/`](docs/) — start with [`docs/architecture.m
 
 ### Continuous integration
 
-Every pull request and every push to `main` runs the same set of checks:
+Every pull request runs the checks below. A check whose verdict cannot change on the tree in
+front of it is path-filtered rather than run to the same answer twice, so the *When* column is
+part of the contract:
 
-| Check | Does | Fails the build |
-|---|---|---|
-| [`ci.yml`](.github/workflows/ci.yml) | ruff → mypy → pytest, on 3.12 **and** 3.13 | yes |
-| [`spec-lint.yml`](.github/workflows/spec-lint.yml) | lints the design specs under `docs/specs/` | yes |
-| [`dependency-review.yml`](.github/workflows/dependency-review.yml) | fails a PR that *introduces* a dependency with a known advisory (`moderate`+) | yes |
-| [`zizmor.yml`](.github/workflows/zizmor.yml) | static analysis of the workflow files themselves | no — reports to code scanning |
-| CodeQL | `python` + `actions`, `extended` query suite; also weekly | no — reports to code scanning |
+| Check | Does | When | Fails the build |
+|---|---|---|---|
+| [`ci.yml`](.github/workflows/ci.yml) | ruff → mypy → pytest, on 3.12 **and** 3.13 | every PR | yes |
+| [`spec-lint.yml`](.github/workflows/spec-lint.yml) | lints the design specs under `docs/specs/` | specs touched | yes |
+| [`dependency-review.yml`](.github/workflows/dependency-review.yml) | fails a PR that *introduces* a dependency with a known advisory (`moderate`+) | every PR | yes |
+| [`zizmor.yml`](.github/workflows/zizmor.yml) | static analysis of the workflow files themselves | workflow, action, dependabot or zizmor config touched; also weekly | no — reports to code scanning |
+| CodeQL | `python` + `actions`, `extended` query suite; also weekly | every PR | no — reports to code scanning |
+
+On a push to `main` the full `ci.yml` matrix still runs, but as the first job of
+[`release.yml`](.github/workflows/release.yml), which `uses:` this same workflow before it is
+allowed to publish — so on main the checks are listed under the *Release* workflow, named
+`test / test (py3.12)` and `test / test (py3.13)`. `ci.yml` deliberately carries no `push`
+trigger of its own; it had one, and the result was that every merge ran the identical matrix
+twice. A `v*` tag is gated the same way, by that same reusable call.
 
 CodeQL runs as GitHub's **default setup** — a repository setting, not a workflow file, which is
 why there is no `codeql.yml` here (adding one would disable the default setup and silently stop

{log_foundry-0.10.2.dev86 → log_foundry-0.10.2.dev87}/pyproject.toml

@@ -20,7 +20,7 @@ dependencies = [
 ]
 
 # Optional features. Install with: pip install log-foundry[aws]
-version = "0.10.2.dev86"
+version = "0.10.2.dev87"
 
 [project.optional-dependencies]
 aws = ["boto3>=1.43.61"]              # SQSSink, SNSSink, KinesisSink, FirehoseSink
@@ -63,6 +63,13 @@ exclude = [
 pytest = "^9.0"
 pytest-asyncio = "^1.4.0"        # for testing async @trace (guide Phase 8)
 pytest-cov = "^7.1.0"
+# The suite is sleep-bound, not CPU-bound: 1,871 tests spend ~116 s of wall clock at 7%
+# CPU, because the bounds this library promises (a 30 s shutdown budget, a backoff, a
+# wedged drain) are proved by waiting for them. Two tests block 30 s each. Distributing
+# across processes therefore buys almost the whole wall clock back — measured 125.9 s ->
+# 40.8 s at `-n 8 --dist load` — where caching the dependency install could only ever
+# save the 18 s that install takes.
+pytest-xdist = "^3.8"
 # Bounded to a minor, not left open. Ruff's DEFAULT rule set is not stable across minors —
 # 0.16.0 widened it from 59 rules to 413 — so an open constraint lets a release change what
 # CI enforces. `[tool.ruff.lint] select` below is the other half: the bound makes the change