Repository navigation
chore: release 3.1.0 - #154
Merged
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
Releases 3.1.0, carrying everything merged since 3.0.0:
to_security_requirementsexported fromidentityand the package root (Export to_security_requirements from identity and the package root #151), which is the new public surface that makes this a minorkeys[](README: UCP profile keys[] is informational #150, docs: correct A2A signing docs and supported versions; drop em-dashes #152)if-necessaryprerelease rule with theweb3<8constraint (uv: let fastapi 0.142 resolve (prerelease if-necessary, web3<8) #149)Also in this PR:
agentscore-pyfloor raised to 2.7.1 (released today), and theweb3<8comment now states the real blocker. web3 8.0.0 is stable, but it needs eth-abi 6, which pympp'stempoextra excludes (eth-abi<6, pympp 0.11.0 is the latest), so an unconstrained re-lock lands on the 8.0.0b3 beta and pinning 8.0.0 downgrades pympp to 0.9.1. I tried the lift: the beta resolution passed the suite, but shipping a beta to merchants is the thing the constraint exists to prevent.Worked with: Varun.
Out of scope: lifting
web3<8, which waits on pympp admitting eth-abi 6.Type of change
Public API
to_security_requirementsis newly exported (merged in #151). Nothing removed or changed.Test plan
ruff check,ruff format --check,ty checkandpytest(1893 passed, 4 skipped, 95.41% coverage) pass locally on this branch.Checklist