Skip to content

📦 deps: Bump typescript from 5.9.3 to 6.0.2#2

Open
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/typescript-6.0.2
Open

📦 deps: Bump typescript from 5.9.3 to 6.0.2#2
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/typescript-6.0.2

Conversation

@dependabot
Copy link
Copy Markdown

@dependabot dependabot bot commented on behalf of github Apr 8, 2026

Bumps typescript from 5.9.3 to 6.0.2.

Release notes

Sourced from typescript's releases.

TypeScript 6.0

For release notes, check out the release announcement blog post.

Downloads are available on:

TypeScript 6.0 Beta

For release notes, check out the release announcement.

Downloads are available on:

Commits

@dependabot @github
Copy link
Copy Markdown
Author

dependabot bot commented on behalf of github Apr 8, 2026

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/typescript-6.0.2 branch from 63f03dd to 0e2439c Compare April 9, 2026 03:19
@s-b-e-n-s-o-n
Copy link
Copy Markdown
Contributor

@dependabot rebase

@dependabot dependabot bot changed the title 📦 deps: bump typescript from 5.9.3 to 6.0.2 📦 deps: Bump typescript from 5.9.3 to 6.0.2 Apr 11, 2026
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/typescript-6.0.2 branch from 0e2439c to 3780142 Compare April 11, 2026 22:05
@s-b-e-n-s-o-n
Copy link
Copy Markdown
Contributor

@dependabot rebase

@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/typescript-6.0.2 branch from 3780142 to e3354fc Compare April 11, 2026 22:37
s-b-e-n-s-o-n added a commit that referenced this pull request Apr 13, 2026
Phase 3 security bundle #2 — the last three security ship-blockers
on the go-live checklist. Each fix is contained to the package that
owns the bug, each has regression coverage, and each is verified
under `-race`.

* 🔒 **Kill the client ACL `/containers/json` amplification vector**
  (`clientacl/cache.go` — new file). Before: every inbound request
  from an allowed CIDR fired a fresh upstream `/containers/json` lookup
  so we could map source IP → caller container. A burst of N concurrent
  requests from one IP amplified into N Docker API calls + N JSON
  decodes, which is both a DoS lever against the Docker daemon and a
  steady tax on normal traffic. After: a tiny in-process cache with
  two defenses stacked:

    - **Singleflight per IP.** Concurrent misses for the same IP share
      one in-flight call via a `chan struct{}` barrier. 16 callers →
      1 upstream call (locked in by
      `TestClientCacheCoalescesConcurrentMissesPerIP`).
    - **10-second success TTL + 256-entry LRU-ish cap.** Sequential
      callers within the window get the cached verdict instantly.
      Errors are never cached so a transient upstream blip recovers on
      the next caller instead of pinning everyone to a stale failure.
      Eviction scrubs expired entries first, then drops the oldest
      surviving entry if still at cap — a proper LRU linked list is
      overkill for a 256-entry cache with a 10-second TTL.

  Six tests exhaustively cover TTL-hit/miss, concurrent coalesce,
  per-IP independence, error non-caching, not-found caching, and
  eviction past cap. Wired in via `newACLDeps` so production gets the
  cache and tests can still inject a fake resolver through `aclDeps`.

* 🐛 **Preserve large integers in ownership body mutation**
  (`ownership/middleware.go:mutateJSONBody`). The old path used
  `json.Unmarshal(body, &decoded)` where `decoded` is
  `map[string]any`, which coerces every JSON number to `float64`.
  Any container-create field above 2^53 — `Memory`, `MemorySwap`,
  `PidsLimit`, `NanoCpus` — silently lost precision on the re-encode
  pass even though ownership itself only writes the `Labels` object.
  Fix: switch to `json.NewDecoder(bytes.NewReader(body)).UseNumber()`
  so numbers decode to `json.Number`, which marshals back verbatim.
  New `TestMutateJSONBodyPreservesLargeIntegers` locks in 2^53+1
  (smallest integer float64 loses) and a near-int64-max MemorySwap
  round-tripping exactly through a Labels-injection mutation.

* 📝 **Document the Docker filter negation story**
  (`ownership/middleware.go:decodeDockerFilters`). The audit flagged
  this as a potential silent-dropper for unknown shapes. Re-read of
  the code shows the `default` branch in the type switch already
  errors out — so the function is fail-fast by design, not a dropper.
  What was missing was the rationale: added a block comment spelling
  out (1) Docker has two wire formats (list and object-with-keys)
  and we handle both, (2) `label!=value` negation is transparent
  because it lives inside the string value and ownership doesn't
  parse `!=`, (3) unknown future shapes return an error so a new
  Docker API encoding surfaces as a rejected request instead of a
  silently weakened ownership check. New `TestDecodeDockerFilters`
  cases pin negation pass-through and rejection of numeric/bool
  filter values.

`go test -race ./...` passes clean, `golangci-lint run ./...`
reports zero issues.
Bumps [typescript](https://github.com/microsoft/TypeScript) from 5.9.3 to 6.0.2.
- [Release notes](https://github.com/microsoft/TypeScript/releases)
- [Commits](microsoft/TypeScript@v5.9.3...v6.0.2)

---
updated-dependencies:
- dependency-name: typescript
  dependency-version: 6.0.2
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/typescript-6.0.2 branch from e3354fc to a1f34a4 Compare April 14, 2026 00:48
@dependabot dependabot bot requested a review from biggest-littlest as a code owner April 14, 2026 00:48
@vercel
Copy link
Copy Markdown

vercel bot commented Apr 14, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
sockguard-website Ready Ready Preview, Comment Apr 14, 2026 0:49am

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