log-foundry 0.10.2.dev123__tar.gz → 0.10.2.dev124__tar.gz

{log_foundry-0.10.2.dev123 → log_foundry-0.10.2.dev124}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: log-foundry
-Version: 0.10.2.dev123
+Version: 0.10.2.dev124
 Summary: Generate logs for your console and JSON events for downstream consumption.
 License-Expression: MIT
 License-File: LICENSE
@@ -1366,8 +1366,8 @@ poetry run python scripts/docstring-lint.py   # the docstring rule over src/ —
 All six run before a push. The last two are the ones to remember, because they are deliberately
 not CI jobs: they hold the documentation and the docstrings to rules a reviewer would otherwise
 have to carry, and keeping them local means the failure lands on whoever caused it rather than on
-a shared branch. Each has a `-test.sh` beside it that proves its own checks still fire; run that
-one too if you change the linter.
+a shared branch. Each of the three linters has a `-test.sh` beside it that proves its own checks
+still fire; run that one too if you change the linter.
 
 The library uses a src layout (`src/log_foundry/`) with a single concept per module: `config`,
 `ids`, `model`, `context`, `decorator`, `api`, `console`, `worker`, `sanitize` and `results`,

{log_foundry-0.10.2.dev123 → log_foundry-0.10.2.dev124}/README.md

@@ -1315,8 +1315,8 @@ poetry run python scripts/docstring-lint.py   # the docstring rule over src/ —
 All six run before a push. The last two are the ones to remember, because they are deliberately
 not CI jobs: they hold the documentation and the docstrings to rules a reviewer would otherwise
 have to carry, and keeping them local means the failure lands on whoever caused it rather than on
-a shared branch. Each has a `-test.sh` beside it that proves its own checks still fire; run that
-one too if you change the linter.
+a shared branch. Each of the three linters has a `-test.sh` beside it that proves its own checks
+still fire; run that one too if you change the linter.
 
 The library uses a src layout (`src/log_foundry/`) with a single concept per module: `config`,
 `ids`, `model`, `context`, `decorator`, `api`, `console`, `worker`, `sanitize` and `results`,

{log_foundry-0.10.2.dev123 → log_foundry-0.10.2.dev124}/pyproject.toml

@@ -74,7 +74,7 @@ keywords = [
 # vulnerability-reporting channel. The repository is still named `log-forge` — the ORIGINAL name,
 # which PyPI rejected for the distribution — so these URLs deliberately do not match the package
 # name. See the note on `name` above before "correcting" them.
-version = "0.10.2.dev123"
+version = "0.10.2.dev124"
 
 [project.urls]
 Homepage = "https://github.com/agriffi10/log-forge"