Remove nonexistent telemetry quota bonus claim - #91
Merged
Conversation
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
app_urltelemetry quota-bonus claim from sync, async, and historical public wordingRECORD1.12.7Red / green
Red first:
Telemetry sends extra application metadata with API requests.then exposed a real matcher false positive and failed independently in both SDKsGreen on exact head
00b8c64bed61b5fcd65d4c671bbb4dd984aac4b2(tree387a3ef556b9ff259fd93eabab8105689a5fcc5c):pip-audit: no known vulnerabilitiesRECORDentrypip check, import/version/interface proof, and live keyless Brent demo smokeExact local candidates:
oilpriceapi-1.12.7-py3-none-any.whl, 53 entries, SHA256c6cc5e6e23b754f691bf442fe51516b4ccfe3a55ece061f437907be3e01d8e24oilpriceapi-1.12.7.tar.gz, 77 entries, SHA256e15cdf0cc5cf839505c37595151976366a59346f746981013288ab7b3b352121Release
Merge through protected main, then publish
v1.12.7only through the existing reviewed PyPI OIDC workflow. Public immutable hashes/provenance, clean PyPI install, authenticated + keyless production smokes, and the scheduled synthetic remain release gates.