chore(deps): update npm minor and patch dependencies - #3764
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
gittensory-ui | 8cea88a | Commit Preview URL Branch Preview URL |
Jul 06 2026, 10:17 AM |
Contributor
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #3764 +/- ##
=======================================
Coverage 93.33% 93.33%
=======================================
Files 317 317
Lines 32433 32433
Branches 11892 11892
=======================================
Hits 30270 30270
Misses 1530 1530
Partials 633 633 🚀 New features to boost your workflow:
|
renovate
Bot
force-pushed
the
renovate/npm-minor-patch
branch
from
July 6, 2026 08:08
6b04753 to
4fa0192
Compare
2 tasks
renovate
Bot
force-pushed
the
renovate/npm-minor-patch
branch
from
July 6, 2026 08:15
4fa0192 to
0489b7d
Compare
This was referenced Jul 6, 2026
renovate
Bot
force-pushed
the
renovate/npm-minor-patch
branch
from
July 6, 2026 08:51
0489b7d to
eef89db
Compare
renovate
Bot
force-pushed
the
renovate/npm-minor-patch
branch
from
July 6, 2026 08:54
eef89db to
282b7e3
Compare
renovate
Bot
force-pushed
the
renovate/npm-minor-patch
branch
from
July 6, 2026 08:57
282b7e3 to
c294eb8
Compare
renovate
Bot
force-pushed
the
renovate/npm-minor-patch
branch
from
July 6, 2026 09:05
c294eb8 to
69268b6
Compare
renovate
Bot
force-pushed
the
renovate/npm-minor-patch
branch
from
July 6, 2026 09:17
69268b6 to
3da9f46
Compare
renovate
Bot
force-pushed
the
renovate/npm-minor-patch
branch
from
July 6, 2026 09:20
3da9f46 to
7054d4e
Compare
renovate
Bot
force-pushed
the
renovate/npm-minor-patch
branch
from
July 6, 2026 09:26
7054d4e to
0a78feb
Compare
renovate
Bot
force-pushed
the
renovate/npm-minor-patch
branch
from
July 6, 2026 09:28
0a78feb to
23250a1
Compare
renovate
Bot
force-pushed
the
renovate/npm-minor-patch
branch
from
July 6, 2026 09:45
23250a1 to
5b67fe4
Compare
renovate
Bot
force-pushed
the
renovate/npm-minor-patch
branch
from
July 6, 2026 09:48
5b67fe4 to
0617aba
Compare
renovate
Bot
force-pushed
the
renovate/npm-minor-patch
branch
from
July 6, 2026 10:00
0617aba to
35c4185
Compare
JSONbored
force-pushed
the
renovate/npm-minor-patch
branch
from
July 6, 2026 10:02
35c4185 to
e1b75ea
Compare
renovate
Bot
force-pushed
the
renovate/npm-minor-patch
branch
from
July 6, 2026 10:02
e1b75ea to
1a56fad
Compare
renovate
Bot
force-pushed
the
renovate/npm-minor-patch
branch
from
July 6, 2026 10:07
1a56fad to
a887d9b
Compare
renovate
Bot
force-pushed
the
renovate/npm-minor-patch
branch
from
July 6, 2026 10:10
a887d9b to
1dae472
Compare
renovate
Bot
force-pushed
the
renovate/npm-minor-patch
branch
from
July 6, 2026 10:12
1dae472 to
208beb4
Compare
…he dependency bump The lockfile's nested entry for @lovable.dev/vite-tanstack-config was still pinned to 2.5.3 while apps/gittensory-ui/package.json already required 2.6.5, failing npm ci. The wrangler devDependency bump also changes cf-typegen's generated output, and the newer prettier changes how a few pre-existing union types get formatted.
JSONbored
force-pushed
the
renovate/npm-minor-patch
branch
from
July 6, 2026 10:15
208beb4 to
8cea88a
Compare
Contributor
Author
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
JSONbored
added a commit
that referenced
this pull request
Jul 16, 2026
…pinned wrangler The previous commit's regeneration silently picked up a stale, globally-installed wrangler (4.103.0, bundling workerd@1.20260617.1) instead of this repo's pinned 4.107.0 (workerd@1.20260701.1) -- node_modules/.bin/wrangler didn't exist yet at that point (fresh worktree, npm ci hadn't run), so `wrangler types` fell through to PATH resolution and found /opt/homebrew/bin/wrangler instead. Not an actual repo-side drift issue: a clean npm ci + regeneration in a fresh worktree confirms origin/main's worker-configuration.d.ts is (and has been) correctly in sync since #3764 -- every commit back through #3835 already references workerd@1.20260701.1.
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.
This PR contains the following updates:
^0.16.17→^0.18.0^1.13.7→^1.19.14^2.0.6→^2.0.81.0.2→1.0.31.1.0→1.1.22.5.3→2.6.5^0.219.0→^0.220.0^2.8.0→^2.9.0^2.8.0→^2.9.0^1.2.14→^1.2.15^1.1.17→^1.1.18^1.1.10→^1.1.11^1.2.0→^1.2.1^1.3.5→^1.3.6^1.1.14→^1.1.15^2.3.1→^2.3.2^1.1.17→^1.1.18^2.1.18→^2.1.19^1.1.17→^1.1.18^2.1.10→^2.1.11^1.1.18→^1.1.19^1.2.16→^1.2.17^1.1.17→^1.1.18^1.1.10→^1.1.11^1.4.1→^1.4.2^1.2.12→^1.2.13^2.3.1→^2.3.2^1.1.10→^1.1.11^1.4.1→^1.4.2^1.3.1→^1.3.2^1.1.15→^1.1.16^1.1.12→^1.1.13^1.1.13→^1.1.14^1.2.10→^1.2.11^10.62.0→^10.63.0^10.62.0→^10.63.0^4.3.1→^4.3.2^5.101.0→^5.101.2^1.170.16→^1.170.17^1.168.26→^1.168.27^1.168.18→^1.168.19^22.10.2→^22.20.0^22.10.0→^22.20.0^22.19.21→^22.20.0^0.16.2→^0.17.3^4.6.14→^4.12.27^4.12.26→^4.12.27^4.2.0→^4.3.0^12.40.0→^12.42.2^8.8.0→^8.9.0^1.61.0→^1.61.13.8.4→3.9.4^3.8.4→^3.9.4^7.79.0→^7.80.0^4.11.2→^4.12.0^4.3.1→^4.3.2^7.5.16→^7.5.19^4.22.4→^4.22.5^5.7.2→^5.9.3^5.6.3→^5.9.3^8.61.1→^8.62.1^8.0.16→^8.1.3^4.102.0→^4.107.0Dependency PRs must keep
npm run test:cipassing. The 97% coverage requirement is enforced as Codecov patch coverage on changed lines (codecov/patch), so dependency-only bumps satisfy it without new tests.GitHub Actions updates must remain SHA-pinned.
Renovate is the sole dependency and security-update bot for this repo; GitHub Dependabot security updates are disabled to avoid duplicate PRs (e.g. the two hono advisory PRs).
Release Notes
cloudflare/workers-sdk (@cloudflare/vitest-pool-workers)
v0.18.0Compare Source
Minor Changes
#14382
fd92d56Thanks @petebacondarwin! - Add support for declarative Durable Object exportswrangler deploynow accepts anexportsmap inwrangler.jsonas a declarative alternative to the legacymigrationsarray.Each entry in
exportsis keyed by Durable Object class name.typecarries the export kind (currently always"durable-object"); thestatefield carries the lifecycle and defaults to"created"(live) when omitted:{ "exports": { // Provision a new Durable Object class (`MyDO`) "MyDO": { "type": "durable-object", "storage": "sqlite" }, // Delete Durable Object class (`OldGone`) "OldGone": { "type": "durable-object", "state": "deleted" }, // Rename a Durable Object class (from `OldName` to `NewName`) "OldName": { "type": "durable-object", "state": "renamed", "renamed_to": "NewName" }, "NewName": { "type": "durable-object", "storage": "sqlite" }, // Transfer a Durable Object (`Outgoing`) to a new Worker (`target-worker`) "Outgoing": { "type": "durable-object", "state": "transferred", "transferred_to": "target-worker" }, // Prepare to receive the transfer of a Durable Object (`Incoming`) from another Worker (`source-worker`) "Incoming": { "type": "durable-object", "state": "expecting-transfer", "storage": "sqlite", "transfer_from": "source-worker" } } }When a Worker declares Durable Object class bindings but no lifecycle for them (neither a
migrationsarray nor anexportsmap), wrangler warns and now suggests a declarativeexportsentry for each class (previously it suggested a legacymigrationsblock).The deployment response now surfaces the server's reconciliation result — created namespaces, applied tombstones, structured per-scenario info entries, and a
removable_entrieshint for stale tombstones that are safe to delete from the config. Blocking errors return the structured per-class detail with scenario tags, suggested remediation, and any referencing-script context.wrangler versions uploadalso forwardsexports. Declarativeexportslifecycle changes are reconciled when the version is deployed (wrangler versions deployorwrangler deploy), so aversions uploadpayload can declare new classes inexportswithout immediately provisioning them. An actor binding (durable_objects.bindings) to a class declared only inexportson the sameversions uploadis rejected with a clear error (code 100406) — the binding cannot be resolved until the namespace is provisioned. Either stage the new class viactx.exports.X(no binding required) onversions uploadand add the binding at deploy time, or usewrangler deployto provision and bind in one step (the same constraint applies to themigrationsflow).Multi-version deploys (
wrangler versions deploy A@50% B@50%) where the selected versions disagree on declarativeexportsare rejected server-side with a clear message: deploy the version that changesexportsat 100% first, then run the percentage-split deploy. This prevents traffic on one branch routing to code that references unprovisioned or just-deleted DO namespaces. Single-version (100%) deploys are unaffected.Local development (
wrangler dev,vite devandunstable_startWorker) reads Durable Object SQLite storage settings from the newexportsfield, so applications using the declarative flow get correct local-dev storage without needing to also declare amigrationsblock.@cloudflare/vitest-pool-workersalso picks up Durable Object configuration fromexports, so tests against anexports-only Worker run with the correct local SQLite storage and can reach unbound Durable Object classes viactx.exports.X.wrangler typesis also aware ofexports. Live entries (includingexpecting-transfer, the receiving side of a two-phase transfer) are added toCloudflare.GlobalProps.durableNamespaces, which typesctx.exports.Xfor unbound Durable Objects declared only viaexports.Patch Changes
aa5d580,6b0ce98,fd92d56,bfe48db,be3f792,0277bfa,98793d8,e1532eb]:v0.17.0Compare Source
Minor Changes
#14490
75d8cb0Thanks @petebacondarwin! - Make Workflow introspectorget()asyncThe
introspectWorkflow(...).get()method now returns a promise, so callers must await it:This aligns Workflow introspection with the shared implementation used by
createTestHarness().Patch Changes
#14490
75d8cb0Thanks @petebacondarwin! - Supportrequire("./x.wasm?module")in CommonJS dependenciesPreviously, only literal
await import("./x.wasm?module")specifiers were rewritten through the static analysis path added in #11094. CommonJS dependencies that userequire("./x.wasm?module")reach the module-fallback service at runtime, where the?modulesuffix went unhandled. The fallback either failed withNo such module "<abs>/x.wasm?module"or, when aCompiledWasmrule was configured, attempted to evaluate the WebAssembly bytes as JavaScript.However, these
require()s work in deployed workers because esbuild's bundler statically rewrites theserequire()calls into ES dynamic imports. vitest-pool-workers' Vite-based pipeline doesn't do that rewrite and instead defers to the module-fallback at runtime.The module-fallback now strips
?modulefrom the resolved target and synthesizes a CommonJS wrapper that re-requires the underlying.wasmby absolute path, exposing it ondefaultto match what workerd produces forCompiledWasmmodules.Updated dependencies [
75d8cb0,75d8cb0,75d8cb0,75d8cb0,75d8cb0,f10d4ad,75d8cb0,75d8cb0,75d8cb0,75d8cb0,d292046,75d8cb0,75d8cb0,75d8cb0,75d8cb0,75d8cb0,75d8cb0,e0cc2cb,75d8cb0,75d8cb0,75d8cb0]:v0.16.20Compare Source
Patch Changes
#14398
c5014ccThanks @apeacock1991! - AddevictDurableObjectandevictAllDurableObjectstest helpers tocloudflare:testThese helpers let you exercise how a Durable Object behaves across evictions in your tests. Eviction is graceful: durable storage is preserved, in-memory state is reset by tearing down the instance, hibernatable WebSockets are hibernated rather than closed, and eviction waits for in-flight requests to drain.
#14394
8a5cf8cThanks @Partha-Shankar! - fix(d1): escapemigrationsTableNameand filenames in SQLite queriesD1 migration commands in both
wranglerand@cloudflare/vitest-pool-workersinterpolated themigrationsTableNameconfig value and migration filenames directly into SQL strings without any escaping. This meant:my"tablewould produce invalid SQL inCREATE TABLE,SELECT, andINSERTstatements, andwhat's-new.sql) would break theINSERT INTO ... VALUES ('...')statement appended after each migration inwrangler.Both identifiers are now properly escaped before interpolation:
migrationsTableNameis wrapped in double-quotes with internal double-quotes doubled (SQL-standard identifier quoting), and migration filenames used as string literals have their single-quotes doubled before insertion.Updated dependencies [
5f40dd5,34e0cef,3b743c1,daa5389,8a5cf8c]:v0.16.19Compare Source
Patch Changes
a085dec,9a0de8f,fab565f,3f02864,4ef872f,2a02858,e312dec]:v0.16.18Compare Source
Patch Changes
c6579d3,444b75e,b38823f,cfd6205,cfd6205]:honojs/node-server (@hono/node-server)
v2.0.8Compare Source
What's Changed
--no-git-checksoption forpnpm stage publishby @yusukebe in #369Full Changelog: honojs/node-server@v2.0.7...v2.0.8
open-telemetry/opentelemetry-js (@opentelemetry/exporter-trace-otlp-http)
v0.220.0Compare Source
radix-ui/primitives (@radix-ui/react-accordion)
v1.2.15@radix-ui/react-primitive@2.1.7,@radix-ui/react-collapsible@1.1.15,@radix-ui/react-collection@1.1.11radix-ui/primitives (@radix-ui/react-alert-dialog)
v1.1.18@radix-ui/react-primitive@2.1.7,@radix-ui/react-dialog@1.1.18radix-ui/primitives (@radix-ui/react-aspect-ratio)
v1.1.11@radix-ui/react-primitive@2.1.7radix-ui/primitives (@radix-ui/react-avatar)
v1.2.1@radix-ui/react-primitive@2.1.7radix-ui/primitives (@radix-ui/react-checkbox)
v1.3.6@radix-ui/react-primitive@2.1.7radix-ui/primitives (@radix-ui/react-collapsible)
v1.1.15@radix-ui/react-primitive@2.1.7radix-ui/primitives (@radix-ui/react-context-menu)
v2.3.2@radix-ui/react-primitive@2.1.7,@radix-ui/react-menu@2.1.19radix-ui/primitives (@radix-ui/react-dialog)
v1.1.18@radix-ui/react-primitive@2.1.7,@radix-ui/react-dismissable-layer@1.1.14,@radix-ui/react-focus-scope@1.1.11,@radix-ui/react-portal@1.1.13radix-ui/primitives (@radix-ui/react-dropdown-menu)
v2.1.19Other updates
@radix-ui/react-primitive@2.1.7,@radix-ui/react-menu@2.1.19radix-ui/primitives (@radix-ui/react-hover-card)
v1.1.18@radix-ui/react-primitive@2.1.7,@radix-ui/react-dismissable-layer@1.1.14,@radix-ui/react-popper@1.3.2,@radix-ui/react-portal@1.1.13radix-ui/primitives (@radix-ui/react-label)
v2.1.11@radix-ui/react-primitive@2.1.7radix-ui/primitives (@radix-ui/react-menubar)
v1.1.19@radix-ui/react-primitive@2.1.7,@radix-ui/react-menu@2.1.19,@radix-ui/react-collection@1.1.11,@radix-ui/react-roving-focus@1.1.14radix-ui/primitives (@radix-ui/react-navigation-menu)
v1.2.17Other updates
@radix-ui/react-primitive@2.1.7,@radix-ui/react-dismissable-layer@1.1.14,@radix-ui/react-collection@1.1.11,@radix-ui/react-visually-hidden@1.2.7radix-ui/primitives (@radix-ui/react-popover)
v1.1.18@radix-ui/react-primitive@2.1.7,@radix-ui/react-dismissable-layer@1.1.14,@radix-ui/react-focus-scope@1.1.11,@radix-ui/react-popper@1.3.2,@radix-ui/react-portal@1.1.13radix-ui/primitives (@radix-ui/react-progress)
v1.1.11@radix-ui/react-primitive@2.1.7radix-ui/primitives (@radix-ui/react-radio-group)
v1.4.2@radix-ui/react-primitive@2.1.7,@radix-ui/react-roving-focus@1.1.14radix-ui/primitives (@radix-ui/react-scroll-area)
v1.2.13Other updates
@radix-ui/react-primitive@2.1.7radix-ui/primitives (@radix-ui/react-select)
v2.3.2Other updates
@radix-ui/react-primitive@2.1.7,@radix-ui/react-dismissable-layer@1.1.14,@radix-ui/react-focus-scope@1.1.11,@radix-ui/react-popper@1.3.2,@radix-ui/react-collection@1.1.11,@radix-ui/react-portal@1.1.13,@radix-ui/react-visually-hidden@1.2.7radix-ui/primitives (@radix-ui/react-separator)
v1.1.11@radix-ui/react-primitive@2.1.7radix-ui/primitives (@radix-ui/react-slider)
v1.4.2Other updates
@radix-ui/react-primitive@2.1.7,@radix-ui/react-collection@1.1.11radix-ui/primitives (@radix-ui/react-switch)
v1.3.2@radix-ui/react-primitive@2.1.7radix-ui/primitives (@radix-ui/react-tabs)
v1.1.16@radix-ui/react-primitive@2.1.7,@radix-ui/react-roving-focus@1.1.14radix-ui/primitives (@radix-ui/react-toggle)
v1.1.13@radix-ui/react-primitive@2.1.7radix-ui/primitives (@radix-ui/react-toggle-group)
v1.1.14@radix-ui/react-primitive@2.1.7,@radix-ui/react-roving-focus@1.1.14,@radix-ui/react-toggle@1.1.13radix-ui/primitives (@radix-ui/react-tooltip)
v1.2.11@radix-ui/react-primitive@2.1.7,@radix-ui/react-dismissable-layer@1.1.14,@radix-ui/react-popper@1.3.2,@radix-ui/react-portal@1.1.13,@radix-ui/react-visually-hidden@1.2.7getsentry/sentry-javascript (@sentry/node)
v10.63.0Compare Source
url.fullattribute to resource spans (#21846)extendIntegrationmethod (#21759)isTracingSuppressedto the async context strategy (#21785)fastifyIntegration(#21706)sentry.status.messageattribute (#21811)Configuration
📅 Schedule: (in timezone America/Phoenix)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.