Take agentscore-py 2.6.0 - #99
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
Raises the
agentscore-pyfloor from>=2.5.2to>=2.6.0, which is the release adding the optionalrefreshablefield toCredentialItem. Nothing in this library reads that field, so this is a floor bump rather than a behavior change.The old floor already resolved 2.6.0, so this does not change what a fresh install gets today. It states the intended baseline explicitly instead, which is what stops a consumer pinning an older SDK and getting a shape this library was not tested against. Matches the node-commerce change.
Patch bump to 2.5.14.
Type of change
Public API
None. No exported type, signature, or wire-format change in this package. The SDK's own addition is
NotRequired, so nothing re-exported through here changes shape.A consumer already on
agentscore-py < 2.6.0will now resolve an upgrade rather than stay put. That upgrade is itself additive.Test plan
uv run pytest(1841 pass, 4 skipped, 95.36% against a 95% floor),uv run ruff check, anduv run ty checkall clean with 2.6.0 installed.uv sync --all-extras --all-groupsused throughout so extras and dev groups resolve.Checklist