obsforge 0.1.2__tar.gz → 0.1.3__tar.gz

{obsforge-0.1.2 → obsforge-0.1.3}/CHANGELOG.md

@@ -7,6 +7,18 @@ All notable changes to obsforge are documented here. Format loosely follows
 
 _Nothing yet._
 
+## [0.1.3] — 2026-06-06
+
+Documentation-only release so the PyPI project page reflects the current docs. No
+code or behavior changes from 0.1.2.
+
+### Changed
+- Documented the **PII scrubbing scope** honestly in the README and SECURITY.md:
+  the exception stacktrace is now covered (since 0.1.2), but pattern scrubbing does
+  not catch IPv6, phone numbers, or generic cloud keys unless under a redacted key
+  name, and key-based redaction does not recurse into nested `extra` dicts.
+- Reconciled stale `0.1.0` references across the docs to the published state.
+
 ## [0.1.2] — 2026-06-06
 
 ### Fixed

{obsforge-0.1.2 → obsforge-0.1.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: obsforge
-Version: 0.1.2
+Version: 0.1.3
 Summary: Zero-infra drop-in structured logging & observability for Python (Grafana/Loki, Elastic, any stack)
 Project-URL: Homepage, https://github.com/AnthonyGrullonA/OBSFORGE
 Project-URL: Repository, https://github.com/AnthonyGrullonA/OBSFORGE
@@ -295,9 +295,17 @@ Full promtail/Alloy + OTLP reference: [docs/operational/loki_otel_setup.md](http
 
 - **No cardinality footguns:** `trace_id`, `user_id`, `tenant_id`, `request_id`,
   `correlation_id`, `session_id`, `event_id` can never be emitted as labels.
-- **PII scrubbing:** emails, bearer/JWT tokens, card numbers, SSNs and IPs are
-  redacted from every string field — message, payload previews, headers,
-  exception text, DB query text.
+- **PII scrubbing:** emails, bearer/JWT tokens, card numbers, SSNs and **IPv4**
+  addresses are pattern-redacted from every string field — message, payload
+  previews, headers, exception message **and stacktrace**, DB query text — and
+  configured `redact_keys` (`password`, `token`, …) are replaced wholesale.
+
+  **Scope (know the edges):** pattern scrubbing covers the shapes above; it does
+  **not** yet catch IPv6, phone numbers, or generic cloud keys (e.g. `AKIA…`)
+  unless they sit under a redacted key name. Key-based redaction applies to
+  top-level fields; secrets buried inside a nested dict passed as a single `extra`
+  value are flattened to a string, so only pattern scrubbing reaches them. Treat
+  redaction as defense-in-depth, not a guarantee — don't deliberately log secrets.
 - **Fail-open:** any error inside the pipeline is logged-and-dropped, never raised
   into your hot path.
 - **Trusted propagation:** inbound identifiers are length- and control-char-validated;

{obsforge-0.1.2 → obsforge-0.1.3}/README.md

@@ -235,9 +235,17 @@ Full promtail/Alloy + OTLP reference: [docs/operational/loki_otel_setup.md](http
 
 - **No cardinality footguns:** `trace_id`, `user_id`, `tenant_id`, `request_id`,
   `correlation_id`, `session_id`, `event_id` can never be emitted as labels.
-- **PII scrubbing:** emails, bearer/JWT tokens, card numbers, SSNs and IPs are
-  redacted from every string field — message, payload previews, headers,
-  exception text, DB query text.
+- **PII scrubbing:** emails, bearer/JWT tokens, card numbers, SSNs and **IPv4**
+  addresses are pattern-redacted from every string field — message, payload
+  previews, headers, exception message **and stacktrace**, DB query text — and
+  configured `redact_keys` (`password`, `token`, …) are replaced wholesale.
+
+  **Scope (know the edges):** pattern scrubbing covers the shapes above; it does
+  **not** yet catch IPv6, phone numbers, or generic cloud keys (e.g. `AKIA…`)
+  unless they sit under a redacted key name. Key-based redaction applies to
+  top-level fields; secrets buried inside a nested dict passed as a single `extra`
+  value are flattened to a string, so only pattern scrubbing reaches them. Treat
+  redaction as defense-in-depth, not a guarantee — don't deliberately log secrets.
 - **Fail-open:** any error inside the pipeline is logged-and-dropped, never raised
   into your hot path.
 - **Trusted propagation:** inbound identifiers are length- and control-char-validated;

{obsforge-0.1.2 → obsforge-0.1.3}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "obsforge"
-version = "0.1.2"
+version = "0.1.3"
 description = "Zero-infra drop-in structured logging & observability for Python (Grafana/Loki, Elastic, any stack)"
 readme = "README.md"
 requires-python = ">=3.11"

{obsforge-0.1.2 → obsforge-0.1.3}/src/obsforge/config/settings.py

@@ -147,7 +147,7 @@ class ObsforgeSettings(BaseModel):
     k8s_cluster_name: str | None = None
     k8s_namespace_name: str | None = None
     k8s_deployment_name: str | None = None
-    telemetry_sdk_version: str = "0.1.2"
+    telemetry_sdk_version: str = "0.1.3"
     min_severity: Severity = Severity.INFO
     redact_keys: set[str] = Field(
         default_factory=lambda: {