Repository navigation
Release 2.1.2 - #157
Merged
Merged
Release 2.1.2#157
Conversation
Contributor
|
Reviewed; no blockers found. |
Contributor
|
Reviewed; no blockers found. |
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.
Release 2.1.2
Patch — hardening batch from the post-2.1.1 sweep. All fixes, no features.
mcp.issueris a full http(s) origin at config load (Validatemcp.issueris a full origin (with scheme) at config load #139 / fix: validate mcp.issuer is a full origin at config load (#139) #152). Fail-fast on schemeless or path/query/fragment/credential-bearing values that previously produced malformed endpoint URLs downstream. Format validation only runs whenmcp.enabledis true.mcp.enabled: trueand a malformedmcp.issuerthat previously started (with broken discovery/endpoint URLs) now refuses to start with a clear error naming the bad value.SENSITIVE_KEY_PATTERNlog redaction for snake_case secret keys #140 / fix: redact snake_case secret keys in option logging (#140) #153).SENSITIVE_KEY_PATTERNnow catches snake_case/kebab secret keys (signing_key_pem,initial_access_token,private_key, …); redaction extracted to a sharedlib/redact.ts; thepluginDefaultsdebug log is now redacted too; non-plain objects (Date/Map/class instances) pass through unmangled.(error as Error).message) #142, Harden (error as Error).message catches across remaining src/lib/mcp/ files #147 / fix: harden catch blocks against non-Error throws (#142, #147) #154). All 16 remaining(error as Error).messagecatch sites now useerror instanceof Error ? error.message : String(error), so a thrown string/null can no longer crash the catch itself; the wrapped ID-token verification error now chains the original viacause.Release mechanics
Merging this bumps
package.jsonto 2.1.2. Publishing a GitHub Release taggedv2.1.2triggersrelease.yml, which publishes to npmlatestvia OIDC trusted publishing.🤖 Generated with Claude Code