build: bump pyfly to v26.07.01#45
Merged
Merged
Conversation
Pick up the pyfly NEVER_REDACT fix: trace_id/span_id correlation keys are no longer mutilated by PII redaction (Presidio PHONE pattern), restoring log↔trace correlation. Bumps the [tool.uv.sources] git tag and the dependency floor; only pyfly changes in the lock.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the pyfly dependency from
v26.06.106tov26.07.01(git tag in[tool.uv.sources]+ dependency floor).Why
26.07.01 carries the NEVER_REDACT fix: PII redaction (Presidio PHONE pattern) could mutilate a
trace_id/span_idhex and silently break log↔trace correlation. The framework now protects the correlation keys with a hardcoded allowlist + redact-before-inject.Scope
uv lockupdates only pyfly (v26.6.106 → v26.7.1, commit 244d3a2b); no other package moves. The PR gate's docker-build smoke validates the image resolves the new tag; merging triggers the multi-arch GHCR publish.