Release 1.6.0 - #565
Open
koic wants to merge 1 commit into
Open
Release 1.6.0#565koic wants to merge 1 commit into
koic wants to merge 1 commit into
Conversation
This release lets an application configure, on the OAuth provider, the requests the flow makes to the authorization server: `token_request_params:` adds the parameters a server requires beyond the grant itself, and `http_client_customizer:` adds middleware to the connection the flow uses for discovery, registration, and token requests, behind a guard that refuses a request leaving the origin the flow asked for. The legacy 2025-03-26 discovery path is now taken only when the server publishes no Protected Resource Metadata: a fetch that failed to reach the server, or that answered `5xx` or `429`, raises `Flow::MetadataUnreachableError` instead, and the metadata served on that path must name the MCP server's origin as its `issuer`. The `client_credentials` and `jwt-bearer` grants run on that path, and a stored refresh token no longer crashes their providers. `MCP::Icon.new` now refuses an icon the specification's schema rejects, such as one without `src` or with `sizes` given as a String. Three entries under "Changed" reject what earlier releases accepted and ship in a minor release under the exceptions described in VERSIONING.md.
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
1 participant
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.
This release lets an application configure, on the OAuth provider, the requests the flow makes to the authorization server:
token_request_params:adds the parameters a server requires beyond the grant itself, andhttp_client_customizer:adds middleware to the connection the flow uses for discovery, registration, and token requests, behind a guard that refuses a request leaving the origin the flow asked for. The legacy 2025-03-26 discovery path is now taken only when the server publishes no Protected Resource Metadata: a fetch that failed to reach the server, or that answered5xxor429, raisesFlow::MetadataUnreachableErrorinstead, and the metadata served on that path must name the MCP server's origin as itsissuer. Theclient_credentialsandjwt-bearergrants run on that path, and a stored refresh token no longer crashes their providers.MCP::Icon.newnow refuses an icon the specification's schema rejects, such as one withoutsrcor withsizesgiven as a String. Three entries under "Changed" reject what earlier releases accepted and ship in a minor release under the exceptions described in VERSIONING.md.Checklist