Repository navigation
chore: bump npm dependencies (2026-10-02) - #881
Merged
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
dmarcheck | 371031b | Oct 11 2026, 09:21 PM |
claude
Bot
force-pushed
the
claude/dep-bump-2026-10-02
branch
from
October 11, 2026 18:23
1d537b1 to
716c85e
Compare
Rebuilt on main after #884 (Dependabot) moved mta-sts-worker's wrangler to 4.147.0 and #895 bumped sharp to 0.35.5 and source-map-js to 1.2.2 (both now already on main). Root (dmarcheck): - @biomejs/biome 2.5.2 -> 2.5.15 - @cloudflare/vitest-pool-workers 0.19.0 -> 0.23.0 - @cloudflare/workers-types 5.20260921.1 -> 5.20261011.1 - @emnapi/core 1.11.1 -> 1.11.3 - @sentry/cloudflare 10.75.1 -> 11.6.0 (major) - @types/node 26.1.0 -> 26.6.5 - hono 4.13.9 -> 4.13.13 - jose 6.2.3 -> 6.2.12 - minimatch 10.2.5 -> 10.2.6 - tsx 4.22.4 -> 4.23.15 - typescript 6.0.3 -> 7.0.2 (major) - wrangler 4.136.1 -> 4.149.0 mta-sts-worker: - @cloudflare/workers-types 5.20261004.1 -> 5.20261011.1 - wrangler 4.147.0 -> 4.149.0 wrangler 4.149 adds default module declarations (*.txt, *.html, *.sql, *.bin, *.wasm) to `wrangler types` output, so worker-configuration.d.ts is regenerated with `npm run types` to keep `npm run typecheck` green. Biome 2.5.15 flags a new noUnsafeOptionalChaining finding in src/dashboard/routes.ts (rewritten to an equivalent guarded optional chain) and reformats two test files. Held back: vitest / @vitest/coverage-v8 5.x, because @cloudflare/vitest-pool-workers 0.23.0 peers on vitest ^4.1. Signed-off-by: Claude <noreply@anthropic.com> Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016b3nTyqPN7GWSZ1uoTgQKp
claude
Bot
force-pushed
the
claude/dep-bump-2026-10-02
branch
from
October 11, 2026 19:06
716c85e to
a5b97cb
Compare
schmug
marked this pull request as ready for review
October 11, 2026 21:20
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.
Requested via Slack thread
Before: Several npm packages in the main Worker and in
mta-sts-workerwere behind their latest releases. Two were a major version behind (Sentry and TypeScript).After: Every dependency is on its latest release except vitest 5, which can't be used yet.
npm auditreports 0 vulnerabilities in both packages. Lint, typecheck, build and the coverage run all pass.Summary
How: I ran
npm outdatedandnpm auditin/and/mta-sts-worker, then bumped everything that still builds. npm regenerated both lockfiles; none were edited by hand.This branch has been rebuilt from current
mainas one commit, twice, because twomaincommits conflicted with its lockfiles:mta-sts-worker'swranglerto 4.147.0.sharpto 0.35.5 andsource-map-jsto 1.2.2, and added asharpoverride tomta-sts-worker.Both of #895's bumps are now on
main, so they are no longer part of this PR.Other changes that come with the bumps:
noUnsafeOptionalChainingfinding. It is fixed insrc/dashboard/routes.tswith an equivalent guarded optional chain ((x as {record?: string} | undefined)?.record ?? null). That code already sits behind atypeof … === "string"check, so runtime behavior doesn't change. Biome also reformatstest/cron-rescan.test.tsandtest/rate-limit-mount-order.test.ts(whitespace only).*.txt,*.html,*.sql,*.bin,*.wasm) to the output ofwrangler types. I regeneratedworker-configuration.d.tswithnpm run typessonpm run typecheck(wrangler types --check) stays green.Bumped
Root (
dmarcheck):@biomejs/biome2.5.2 -> 2.5.15@cloudflare/vitest-pool-workers0.19.0 -> 0.23.0@cloudflare/workers-types5.20260921.1 -> 5.20261011.1@emnapi/core1.11.1 -> 1.11.3@sentry/cloudflare10.75.1 -> 11.6.0 (major)@types/node26.1.0 -> 26.6.5hono4.13.9 -> 4.13.13jose6.2.3 -> 6.2.12minimatch10.2.5 -> 10.2.6tsx4.22.4 -> 4.23.15typescript6.0.3 -> 7.0.2 (major)wrangler4.136.1 -> 4.149.0mta-sts-worker:@cloudflare/workers-types5.20261004.1 -> 5.20261011.1wrangler4.147.0 -> 4.149.0Held back
vitest4.1.11 -> 5.0.3 and@vitest/coverage-v84.1.11 -> 5.0.3:@cloudflare/vitest-pool-workers0.23.0 (latest) hasvitest ^4.1as a peer dependency, so vitest 5 has to wait for a pool-workers release that supports it.Owner / zone steps
None. This PR touches
package.json/package-lock.json, which are CODEOWNERS-gated (dependency supply chain), so it needs a code-owner review. Two majors are worth a quick look:tsc --noEmitis clean.Security notes
npm auditis clean in both packages, and so isnpm audit --audit-level=high --omit=dev(the CI gate). The only source change is the equivalent optional-chain rewrite above.Testing
npm run lint: passnpm run typecheck(wrangler types --check + tsc 7.0.2): passwrangler deploy --dry-run: pass for both the root Worker andmta-sts-workervitest run(workers + node projects): 1847 passed, 1 failed out of 1848. The failure istest/integration/mta-sts-runtime.test.ts("successfully fetches and parses the dmarc.mx MTA-STS policy"), which fetches the livedmarc.mxMTA-STS policy. The sandbox this was built in has restricted network egress, and the test also fails there on unmodifiedmain. CI shows whether it passes with real network access.vitest run --project=node --coverage(including the per-file coverage floors): 1809/1809 passedRefs
Routine dependency maintenance; no linked issue.
🤖 Generated with Claude Code
https://claude.ai/code/session_016b3nTyqPN7GWSZ1uoTgQKp
Generated by Claude Code