Skip to content

Dependency refresh: Alpine 3.24.2 pins, deps-watch publish gate, MCP SDK 2.3.1 (alpha.41 candidate) - #91

Merged
AlbSar merged 5 commits into
mainfrom
deps/tazeleme-2026-10-15
Oct 15, 2026
Merged

AlbSar merged 5 commits into
mainfrom
deps/tazeleme-2026-10-15

Conversation

@AlbSar

@AlbSar AlbSar commented Oct 15, 2026

Copy link
Copy Markdown
Contributor

Owner 2026-10-15 decisions after the first manual deps-watch dispatch (platform-verification run 38779130973):

  1. Pins (7e00845): Alpine 3.24.2 host closure (libcrypto3/libssl3 3.5.9-r0, zlib 1.3.2-r1). The local refresh-bwrap result matches the dispatch candidate (branch hash febba56facfe513a). Bundled binary unchanged.
  2. Publish gate (7780dc3 + feec415): deps-publish runs on refresh-verified plus integrity-clear (registry signatures complete, no CRITICAL finding, watch complete) instead of the whole job result. Ordinary advisories keep the watch red but no longer block the pin PR. The second commit closes a fail-open that a security review flagged on the first.
  3. MCP SDK 2.3.1 (e0d532b): the 2.3.1 tarballs still embed fast-uri 3.1.0. The accepted risk moves to the 2.3.1 carriers and adds GHSA-hrr3. The ajv stub guard was mutation-checked: build:dist refuses when the stub is disabled. source-map-js 1.2.2 (dev).
  4. Release bump (27f74c6): alpha.41 Unreleased; alpha.40 recorded as released.

Local deps-watch: CRITICAL 0, HIGH 0, MITIGATED 18, exit 0.

🤖 Generated with Claude Code

https://claude.ai/code/session_017uL4HZTS1oaVHovPUKoRXP

AlbSar and others added 5 commits October 15, 2026 21:11
…3 3.5.9-r0, zlib 1.3.2-r1)

Found by the first manual deps-watch dispatch (platform-verification
run 38779130973). That run's verified candidate and this local
refresh-bwrap run are identical (branch hash febba56facfe513a). Both
independent builds matched, and the bundled binary identity is
unchanged; only the build host closure moved.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017uL4HZTS1oaVHovPUKoRXP
…ed pin PR

The first manual dispatch (run 38779130973) verified an Alpine 3.24.2 pin
candidate, but deps-publish was skipped because it required the whole
deps-watch job to succeed and that job's dependency report failed on
unrelated findings. The refresh step now sets a job output only when
refresh-bwrap exits 0. deps-publish runs on that output (not on the job
result), so the watch job stays red and visible while the pin PR is
still opened. Permissions, the base-sha checkout and never-merge are
unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017uL4HZTS1oaVHovPUKoRXP
…urity review of 7780dc3)

Gating deps-publish only on the verified refresh failed open: before
7780dc3 a signature problem or a CRITICAL (malware) finding blocked the
publisher through the job result, and after it nothing did. A new
integrity step (`deps-watch.mjs --integrity`, reading the newest report)
sets `integrity-clear` only when registry signatures are complete
(invalid 0, missing 0), no finding is CRITICAL and the watch is not
incomplete. deps-publish needs both refresh-verified and
integrity-clear. Ordinary HIGH/MEDIUM advisories keep the job red but no
longer hold back a verified pin candidate. A missing or unreadable
report counts as not clear. The 2026-10-15 dispatch report is clear
(HIGH advisories only).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017uL4HZTS1oaVHovPUKoRXP
…llows; source-map-js 1.2.2 (dev)

Owner 2026-10-15: integrate SDK 2.3.1. Its tarballs still embed
fast-uri 3.1.0 (and ajv 8.18.0) in ajvProvider. The accepted risk moves
to the 2.3.1 carriers and adds GHSA-hrr3-gc8f-f4qj (MEDIUM, the same
host-confusion class); the mitigation is unchanged (not shipped +
Deckent's own validator) and the expiry stays 2026-10-29.
@modelcontextprotocol/core moves 2.2.0 -> 2.3.1 with it. The SDK's
nested zod is now 4.6.7; embedded component lists are unchanged
(check-embedded-deps).
Evidence: typecheck clean; the local deps-watch reports CRITICAL 0,
HIGH 0, MITIGATED 18, exit 0. build:dist is publishable and its SBOM
names no ajv/fast-uri. Mutation: disabling the ajv stub makes build:dist
refuse "would ship the MCP SDK's ajv/fast-uri (FASTURI-OUT)". 59 MCP,
validator, dist and workflow test files pass, after one expectation
was updated from the server@2.2.0 carrier name to 2.3.1.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017uL4HZTS1oaVHovPUKoRXP
…alpha.40 recorded as released

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017uL4HZTS1oaVHovPUKoRXP
@AlbSar
AlbSar merged commit b63d92c into main Oct 15, 2026
25 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant