chore: upgrade logspark to 0.11.0 and python-json-logger to 4.x#150
Merged
Conversation
….1.0 release Pin logspark[json]~=0.11.0 (was >=0.10.2, unbounded) and align python-json-logger to >=4.0,<5.0 as required by the new logspark[json] extra. Resolves uv.lock to logspark 0.11.0 + python-json-logger 4.1.0.
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.
Summary
logspark[json]~=0.11.0(was>=0.10.2with no ceiling — was resolving to the yanked 1.1.0 on fresh installs)python-json-logger>=4.0,<5.0to match the new logspark 0.11.0[json]extra requirement (was>=2.0,<4.0, which conflicts with logspark 0.11.0)python-json-loggeras an explicit direct dependency so it is guaranteed present regardless of how logspark extras resolveuv.lockto logspark 0.11.0 + python-json-logger 4.1.0Why now
logsparkpublished 0.11.0 today and simultaneously the existing 1.1.0 tag is yanked (invalid). Without an upper bound,>=0.10.2was resolving to 1.1.0 on fresh installs. This PR locks us into the supported 0.11.x series.Downstream
After this merges,
v6.1.0will be tagged onreleaseto publish to PyPI, followed by a version bump across all 6.x downstream repos.End-user impact
No API changes. This is a dependency hygiene fix — existing consumers get a stable, non-yanked logspark install.