build(deps): bump @modelcontextprotocol/sdk from 1.29.0 to 1.30.0 - #9
Merged
Mearman merged 1 commit intoSep 8, 2026
Merged
Conversation
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/modelcontextprotocol/sdk-1.29.0
branch
2 times, most recently
from
April 28, 2026 18:01
3ebf223 to
48a96d3
Compare
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/modelcontextprotocol/sdk-1.29.0
branch
from
May 21, 2026 11:22
48a96d3 to
9775408
Compare
dependabot
Bot
changed the title
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/modelcontextprotocol/sdk-1.29.0
branch
2 times, most recently
from
May 25, 2026 13:45
d9d7d7a to
ff6484e
Compare
Member
|
@dependabot rebase |
Bumps [@modelcontextprotocol/sdk](https://github.com/modelcontextprotocol/typescript-sdk) from 1.29.0 to 1.30.0. - [Release notes](https://github.com/modelcontextprotocol/typescript-sdk/releases) - [Commits](modelcontextprotocol/typescript-sdk@v1.29.0...1.30.0) --- updated-dependencies: - dependency-name: "@modelcontextprotocol/sdk" dependency-version: 1.29.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
changed the title
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/modelcontextprotocol/sdk-1.29.0
branch
from
September 8, 2026 22:11
ff6484e to
b5b1162
Compare
Mearman
deleted the
dependabot/npm_and_yarn/modelcontextprotocol/sdk-1.29.0
branch
September 8, 2026 22:12
|
🎉 This PR is included in version 1.25.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
mavrikfalkon
added a commit
to mavrikfalkon/agent-comms
that referenced
this pull request
Sep 12, 2026
…S origin check codex's review of 28bfa22 found isSameOriginUpgrade only accepted http://127.0.0.1:<port>, while runWeb()'s own standalone-CLI banner advertises http://localhost:<port> for the exact same server - a dashboard opened via that URL had its own chat WebSocket rejected with 403. Confirmed by reading both: server.ts's runWeb listener prints the localhost banner, isSameOriginUpgrade compared against a single hardcoded 127.0.0.1 origin string. Fixed with an explicit loopback-hostname allowlist (127.0.0.1, localhost) checked against the parsed Origin's hostname and port, not a bare Host-header trust - still rejects any other origin exactly as before. New test opens a WS with Origin: http://localhost:<port> and confirms it succeeds. Verified: tsc clean, eslint clean, full web-server.integration.test.ts 14/14, full npm test 49/50 (same pre-existing ExaDev#9 Windows failure, unrelated). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
mavrikfalkon
added a commit
to mavrikfalkon/agent-comms
that referenced
this pull request
Sep 12, 2026
…script (bug ExaDev#10) The build script's last step piped printf | cat | mv to prepend #!/usr/bin/env node to dist/cli.js — POSIX-only utilities, so a plain npm run build from cmd.exe or PowerShell failed outright, same class of bug as the husky hooks fixed earlier tonight. src/cli.ts has no shebang of its own and tsc doesn't add one, so this step is the only source of it, and it's still needed: npm's POSIX bin-linking for the published agent-comms binary depends on it. Can't just drop it. Replaced with scripts/add-shebang.ts: reads dist/cli.js, prepends the shebang only if not already present (idempotent), and chmods 0o755 on POSIX only (the mode bit is meaningless on Windows — see ExaDev#9). Runs via plain node/tsx on any OS. Verified: tsc clean, eslint clean, ran the actual remaining build steps (tsc, copy-web-assets, add-shebang) end to end and confirmed dist/cli.js has the shebang and still runs (--help works), confirmed idempotent by running the script twice, full npm test 49/50 (same pre-existing ExaDev#9 Windows failure, unrelated). Could not run the full 'npm run build' end-to-end on this machine — pnpm itself isn't installed here, a pre-existing, unrelated gap that fails before reaching this step either way. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
mavrikfalkon
added a commit
to mavrikfalkon/agent-comms
that referenced
this pull request
Sep 12, 2026
…Dev#9) NTFS has no POSIX mode bits, so fs.writeFileSync's mode option is a no-op on Windows beyond a crude read-only flag - the OS always reports ~0o666 regardless of what identity-store.ts requested, which isn't a real security gap (protection there comes from NTFS ACLs on the parent directory instead), just a platform mismatch in the test's assertion. Skips the assertion on win32 with an explicit reason (t.skip, not a silent pass); the strict 0o600 check is unchanged on POSIX, and the skip message makes no claim of validating NTFS ACLs. Authored by codex (agent-comms mesh); committed after independent review - re-ran tsc, eslint, and the full test suite myself. First fully green run tonight: 49 passed, 0 failed, 1 explicit skip. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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.
Bumps @modelcontextprotocol/sdk from 1.29.0 to 1.30.0.
Release notes
Sourced from @modelcontextprotocol/sdk's releases.
Commits
2d889f2chore: bump version to 1.30.0 (#2563)e3f3daaFix SSE keep-alive timer lifecycle in Streamable HTTP server transport (v1.x)...bb5a718fix(deps): widen@hono/node-serverpast GHSA-frvp-7c67-39w9 (#2549)1dad263fix: send SSE keep-alive comment frames from Streamable HTTP server transport...69749aaValidate Content-Type by parsed media type instead of substring match (v1.x) ...369513dfix: support Zod 3.25 method literals (#2368)e7ee57cv1 stdio buffer limit (#2239)c36e1efAdd end-to-end test suite (#2167)bf1e022chore(ci): switch publish to OIDC trusted publishing (#1839)9edbab7fix(server): prioritize zod issues and format them (#1503)Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for
@modelcontextprotocol/sdksince your current version.