-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Comparing changes
Open a pull request
base repository: modelcontextprotocol/typescript-sdk
base: main
head repository: gleanwork/typescript-sdk
compare: patches
- 13 commits
- 6 files changed
- 2 contributors
Commits on Jun 12, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 3b2bcf2 - Browse repository at this point
Copy the full SHA 3b2bcf2View commit details -
Merge pull request #1 from gleanwork/hjdivad/fallback-to-openid-confi…
…guration fix: fall back to openid-configuration
Configuration menu - View commit details
-
Copy full SHA for 90d0e09 - Browse repository at this point
Copy the full SHA 90d0e09View commit details -
Configuration menu - View commit details
-
Copy full SHA for d1e115f - Browse repository at this point
Copy the full SHA d1e115fView commit details -
Merge pull request #2 from gleanwork/hjdivad/publish
build(publish): workflow to publish fork
Configuration menu - View commit details
-
Copy full SHA for 8b618f8 - Browse repository at this point
Copy the full SHA 8b618f8View commit details -
build(publish): rename package
`@modelcontextprotocol/sdk` -> `@gleanwork/mcp-sdk`
Configuration menu - View commit details
-
Copy full SHA for e40387f - Browse repository at this point
Copy the full SHA e40387fView commit details -
Merge pull request #3 from gleanwork/hjdivad/rename-package
build(publish): rename package
Configuration menu - View commit details
-
Copy full SHA for 9206758 - Browse repository at this point
Copy the full SHA 9206758View commit details -
Revert "build(publish): rename package"
This reverts commit e40387f.
Configuration menu - View commit details
-
Copy full SHA for 7133d44 - Browse repository at this point
Copy the full SHA 7133d44View commit details -
build(publish): publish at longer URLs
We don't want to publish at pkg.pr.new/@modelcontextprotocol/sdk. We want to make it clear it's a fork and publish at pkr.pr.new/gleanwork/typescript-sdk/@modelcontextprotcool/sdk.
Configuration menu - View commit details
-
Copy full SHA for b38225f - Browse repository at this point
Copy the full SHA b38225fView commit details -
Merge pull request #5 from gleanwork/hjdivad/revert-rename
Revert rename + publish to long URLs
Configuration menu - View commit details
-
Copy full SHA for 8f6ea2a - Browse repository at this point
Copy the full SHA 8f6ea2aView commit details -
Configuration menu - View commit details
-
Copy full SHA for fc8ee1c - Browse repository at this point
Copy the full SHA fc8ee1cView commit details -
Merge pull request #6 from gleanwork/hjdivad/readme
docs: update README
Configuration menu - View commit details
-
Copy full SHA for 0fcb3ef - Browse repository at this point
Copy the full SHA 0fcb3efView commit details
Commits on Jul 22, 2025
-
fix: OpenID configuration lookup
OpenID connect and OAuth Authorization Server Metadata use two different schemas for determining the final well-known URL. For servers with path components, the ".well-known" segment is inserted between the host and path component for OAuth authorization server metadata, but appended for openid-connect. e.g. for issuer https://example.com/my-issuer - https://example.com/.well-known/oauth-authorization-server/my-issuer - https://example.com/my-issuer/.well-known/openid-configuration [^1]: https://openid.net/specs/openid-connect-discovery-1_0.html#ProviderConfig [^2]: https://datatracker.ietf.org/doc/html/rfc8414#section-3
Configuration menu - View commit details
-
Copy full SHA for 19a36d6 - Browse repository at this point
Copy the full SHA 19a36d6View commit details -
Merge pull request #7 from gleanwork/hjdivad/fix-openid-configuration…
…-lookup fix: OpenID configuration lookup
Configuration menu - View commit details
-
Copy full SHA for acc52bd - Browse repository at this point
Copy the full SHA acc52bdView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff main...patches