Conversation
|
Claude finished @workers-devprod's task —— View job Changeset Review
I reviewed all 17 changesets against the guidelines in Blocking Issues1. Insufficient documentation for minor features The following changesets are marked as
Per the guidelines: "For new features or significant changes, include a brief usage example. This helps users understand how to use the new functionality." These should include at least a basic example of how users can use Vike/Waku support (e.g., what command to run, what gets configured). Non-blocking Concerns2. Questionable version type
This sounds like an internal implementation detail for analytics rather than a user-facing feature. The guidelines suggest that internal refactoring without user-facing impact doesn't require a changeset. If this truly has no user-facing impact, it should either:
What looks good ✓
|
9a3033c to
eb7afae
Compare
create-cloudflare
@cloudflare/kv-asset-handler
miniflare
@cloudflare/pages-shared
@cloudflare/unenv-preset
@cloudflare/vite-plugin
@cloudflare/vitest-pool-workers
@cloudflare/workers-editor-shared
@cloudflare/workers-utils
wrangler
commit: |
9f91ebd to
35facc3
Compare
fec54df to
76a6b03
Compare
1949c6f to
f05d3ec
Compare
f05d3ec to
8c60ed8
Compare
67b181c to
9007ac3
Compare
9007ac3 to
57833dd
Compare
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
create-cloudflare@2.62.0
Minor Changes
#11549
d059f69Thanks @dario-piotrowicz! - Support Vike in--experimentalmode#11692
df1f9c9Thanks @dario-piotrowicz! - Support Waku in--experimentalmodePatch Changes
faf8d27Thanks @dario-piotrowicz! - Remove redundant output present for the experimental setup of frameworks (by using new CLI flags ofwrangler setup).miniflare@4.20260103.0
Minor Changes
#11648
eac5cf7Thanks @pombosilva! - Add Workflows test handlers in vitest-pool-workers to get the Workflow instance output and error:getOutput(): Returns the output of the successfully completed Workflow instance.getError(): Returns the error information of the errored Workflow instance.Example:
Patch Changes
#11714
65d1850Thanks @dependabot! - chore: update dependencies of "miniflare" packageThe following dependency versions have been updated:
#11732
1615fceThanks @dependabot! - chore: update dependencies of "miniflare" packageThe following dependency versions have been updated:
#11748
b2769bfThanks @dependabot! - chore: update dependencies of "miniflare" packageThe following dependency versions have been updated:
#11791
554a4dfThanks @dependabot! - chore: update dependencies of "miniflare" packageThe following dependency versions have been updated:
#11642
8eede3fThanks @petebacondarwin! - Fix intermittent "Fetch failed" errors in Miniflare tests on WindowsMiniflare tests would occasionally fail with "Fetch failed" errors (particularly on Windows CI runners) due to race conditions between undici's Keep-Alive mechanism and the Miniflare server closing idle connections. Miniflare now configures the Dispatcher to prevent connection reuse and eliminate these race condition errors.
#11493
6a05b1cThanks @GameRoMan! - Updatezodfrom 3.22.3 to 3.25.76@cloudflare/unenv-preset@2.8.0
Minor Changes
#11733
62fd118Thanks @petebacondarwin! - Add support for nativenode:inspectormodule when theenable_nodejs_inspector_modulecompatibility flag is enabled. This feature is currently experimental and requires both theenable_nodejs_inspector_moduleandexperimentalcompatibility flags to be set.To enable the native inspector module, add the following to your
wrangler.jsonc:{ "compatibility_flags": ["experimental", "enable_nodejs_inspector_module"], }Then you can import and use the inspector module in your Worker:
#11744
a7e9f80Thanks @petebacondarwin! - Add support for nativenode:inspector/promisesmodule when theenable_nodejs_inspector_modulecompatibility flag is enabled. This extends the existingnode:inspectorsupport to include the promises-based API.To enable the native inspector/promises module, add the following to your
wrangler.jsonc:{ "compatibility_flags": ["experimental", "enable_nodejs_inspector_module"], }Then you can import and use the inspector/promises module in your Worker:
@cloudflare/vite-plugin@1.20.0
Minor Changes
#11620
25f6672Thanks @dario-piotrowicz! - Expose a newgetLocalWorkerdCompatibilityDateutility that allows callers to get the compatibility date of the locally installedworkerdpackage.#11723
3455912Thanks @jamesopstad! - Add a postbuildApphook that builds Worker environments that haven't already been built.This ensures that auxiliary Workers are included in the build when using full-stack frameworks that define their own
builder.buildAppfunction. Note that this feature is not supported with Vite 6 as thebuildApphook was introduced in Vite 7.#11738
c54f8daThanks @jamesopstad! - Add defaultTextmodule rule for.sqlfiles.This enables importing
.sqlfiles directly in Wrangler and the Cloudflare Vite plugin without extra configuration.Patch Changes
#11815
70ef3edThanks @jamesopstad! - SetignoreOutdatedRequeststotrueinoptimizeDepsconfig.This is a workaround for Optimizer behaviour change leading to errors vitejs/vite#20867 and will resolve
Error: There is a new version of the pre-bundle for ...errors that some users are experiencing. The longer term solution is to use full-bundle mode rather thanoptimizeDepsonce it is supported for server environments. Vite v7.3.1 or above is needed for this change to take effect.#11735
dd66dcdThanks @jamesopstad! - RemovetopLevelNameandnamewhen passingentryWorkerConfigto theconfigfunction for auxiliary Workers.The
namefor each Worker should be unique and thetopLevelNameis computed rather than provided directly.#11720
0457de6Thanks @jamesopstad! - fix: regression where plain class and object types were no longer supported as Durable Objects and Worker entrypointsUpdated dependencies [
02fbd22,b993d95,f612b46,77078ef,2510723,65d1850,1615fce,b2769bf,554a4df,9f6dd71,8eede3f,d123ad0,9e360f6,5121b23,82e7e90,6a05b1c,62fd118,a7e9f80,fc95831,b0dbf1a,4688f59,69979a3,c54f8da,df1f9c9,d059f69,eac5cf7,b827893]:@cloudflare/vitest-pool-workers@0.12.0
Minor Changes
#11648
eac5cf7Thanks @pombosilva! - Add Workflows test handlers in vitest-pool-workers to get the Workflow instance output and error:getOutput(): Returns the output of the successfully completed Workflow instance.getError(): Returns the error information of the errored Workflow instance.Example:
Patch Changes
#11681
1223663Thanks @ascorbic! - Fix vitest-pool-workers hanging when the default inspector port (9229) is already in use. When debugging is enabled and the default port is unavailable, the pool now automatically finds the next available port. If a user explicitly specifies an inspector port that is unavailable, an error is thrown with a clear message.Updated dependencies [
02fbd22,b993d95,f612b46,77078ef,2510723,65d1850,1615fce,b2769bf,554a4df,9f6dd71,8eede3f,d123ad0,9e360f6,5121b23,82e7e90,6a05b1c,fc95831,b0dbf1a,4688f59,69979a3,c54f8da,df1f9c9,d059f69,eac5cf7,b827893]:@cloudflare/workers-utils@0.6.0
Minor Changes
#11702
f612b46Thanks @gpanders! - Add support for trusted_user_ca_keys in WranglerYou can now configure SSH trusted user CA keys for containers. Add the following to your wrangler.toml:
This allows you to specify CA public keys that can be used to verify SSH user certificates.
#11620
25f6672Thanks @dario-piotrowicz! - Expose a newgetLocalWorkerdCompatibilityDateutility that allows callers to get the compatibility date of the locally installedworkerdpackage.#11616
fc95831Thanks @NuroDev! - Add type generation support towrangler devYou can now have your worker configuration types be automatically generated when the local Wrangler development server starts.
To use it you can either:
--typesflag when runningwrangler dev.dev.generate_typesboolean property.{ "$schema": "node_modules/wrangler/config-schema.json", "name": "example", "main": "src/index.ts", "compatibility_date": "2025-12-12", "dev": { "generate_types": true } }#11620
25f6672Thanks @dario-piotrowicz! - Expose newisCompatDateutility that discerns whether a string represents a compatibility date or notPatch Changes
#11737
2cfea12Thanks @NuroDev! - Fix thetriggersJSON schema default value to use valid JSON ({"crons":[]}) instead of an invalid JavaScript literal, which was causing IDE auto-completion to insert a string rather than an object.#11651
d123ad0Thanks @dario-piotrowicz! - Surface error in diagnostics when TOML date/time values are used invarsTOML parses unquoted date/time values like
DATE = 2024-01-01as TOML Date, Date-Time, and Time values. The config validation now surfaces an error in the diagnostics result when this type of values are encountered, with a clear message telling you to quote the value as a string, e.g.DATE = "2024-01-01".#11693
385ec7fThanks @vicb! - Update the signature of ParseTOML to drop the Generics.Use an explicit cast where required.
wrangler@4.57.0
Minor Changes
#11682
b993d95Thanks @ascorbic! - Addwrangler auth tokencommand to retrieve your current authentication credentials.You can now retrieve your authentication token for use with other tools and scripts:
The command returns whichever authentication method is currently configured:
wrangler login(automatically refreshed if expired)CLOUDFLARE_API_TOKENenvironment variableUse
--jsonto get structured output including the token type, which also supports API key/email authentication:This is similar to
gh auth tokenin the GitHub CLI.#11702
f612b46Thanks @gpanders! - Add support for trusted_user_ca_keys in WranglerYou can now configure SSH trusted user CA keys for containers. Add the following to your wrangler.toml:
This allows you to specify CA public keys that can be used to verify SSH user certificates.
#11437
9e360f6Thanks @ichernetsky-cf! - Drop deprecated containersobservability.loggingfield#11616
fc95831Thanks @NuroDev! - Add type generation support towrangler devYou can now have your worker configuration types be automatically generated when the local Wrangler development server starts.
To use it you can either:
--typesflag when runningwrangler dev.dev.generate_typesboolean property.{ "$schema": "node_modules/wrangler/config-schema.json", "name": "example", "main": "src/index.ts", "compatibility_date": "2025-12-12", "dev": { "generate_types": true } }#11524
b0dbf1aThanks @penalosa! - Add hidden CLI flags towrangler setupfor suppressing outputTwo new hidden flags have been added to
wrangler setup:--no-completion-message: Suppresses the deployment details message after setup completes--no-install-wrangler: Skips Wrangler installation during project setup#11777
69979a3Thanks @MattieTK! - Add analytics properties to secret commands for better usage insightsSecret commands (
wrangler secret put,wrangler secret bulk, and their Pages/versions equivalents) now include additional analytics properties to help understand how secrets are being managed:secretOperation: Whether this is a "single" or "bulk" secret operationsecretSource: How the secret was provided ("interactive", "stdin", or "file")secretFormat: For bulk operations, the format used ("json" or "dotenv")hasEnvironment: Whether an environment was specifiedThese properties help improve the developer experience by understanding common usage patterns. No sensitive information (secret names, values, or counts) is tracked.
#11738
c54f8daThanks @jamesopstad! - Add defaultTextmodule rule for.sqlfiles.This enables importing
.sqlfiles directly in Wrangler and the Cloudflare Vite plugin without extra configuration.#11692
df1f9c9Thanks @dario-piotrowicz! - Support Waku in autoconfig#11549
d059f69Thanks @dario-piotrowicz! - Support Vike in autoconfigPatch Changes
#11683
02fbd22Thanks @ascorbic! - Display a warning when authentication errors occur and theaccount_idin your Wrangler configuration does not match any of your authenticated accounts. This helps identify configuration issues where you may have the wrong account ID set in yourwrangler.tomlorwrangler.jsoncfile.#11704
77078efThanks @dario-piotrowicz! - Fix autoconfig handling of Next.js apps with CJS config files and incompatible Next.js versionsPreviously,
wrangler setupandwrangler deploy --x-autoconfigwould fail when working with Next.js applications that use CommonJS config files (next.config.cjs) or have versions of Next.js that don't match the required peer dependencies. The autoconfig process now uses dynamic imports and forced installation to handle these scenarios gracefully.#11796
2510723Thanks @dario-piotrowicz! -wrangler deploydelegates toopennextjs-cloudflare deployonly when the--x-autoconfigflag is usedThe
wrangler deploycommand has been updated to delegate to theopennextjs-cloudflare deploycommand when run in an open-next project. Once this behavior had been introduced it caused a few issues. So it's been decided to enable it for the time being only when the--x-autoconfigflag is set (since this behavior, although generally valid, is only strictly necessary for thewrangler deploy's autoconfig flow).#11764
9f6dd71Thanks @terakoya76! - Fix R2 Data Catalog snapshot-expiration API field namesThe
wrangler r2 bucket catalog snapshot-expiration enablecommand was sending incorrect field namesto the Cloudflare API, resulting in a 422 Unprocessable Entity error. This fix updates the API request
body to use the correct field names:
olderThanDays->max_snapshot_age(as duration string, e.g., "30d")retainLast->min_snapshots_to_keepThe CLI options (
--older-than-daysand--retain-last) remain unchanged.#11651
d123ad0Thanks @dario-piotrowicz! - Surface a more helpful error message for TOML Date, Date-Time, and Time values invarsTOML parses unquoted date/time values like
DATE = 2024-01-01as objects. Previously this would cause an unhelpful error message further down the stack. Now wrangler surfaces a more helpful error message earlier, telling you to quote the value as a string, e.g.DATE = "2024-01-01".#11711
5121b23Thanks @southpolesteve! - Show an error when D1 migration commands are run without a configuration filePreviously, running
wrangler d1 migrations apply,wrangler d1 migrations list, orwrangler d1 migrations createin a directory without a Wrangler configuration file would silently exit with no feedback. Now these commands display a clear error message:"No configuration file found. Create a wrangler.jsonc file to define your D1 database."
#11710
82e7e90Thanks @dario-piotrowicz! - Fix arguments passed towrangler deploynot being forwarded toopennextjs-cloudflare deploywrangler deployrun in an open-next project delegates toopennextjs-cloudflare deploy, as part of this all the arguments passed towrangler deployneed be forwarded toopennextjs-cloudflare deploy, before the arguments would be lost, now they will be successfully forwarded (for examplewrangler deploy --keep-varswill callopennextjs-cloudflare deploy --keep-vars)#10750
4688f59Thanks @jacoblearned! - Notify user on local dev server reload.When running
wrangler dev, the local server suppresses Miniflare's reload messages to prevent duplicate log entries from the proxy and user workers. This update adds a reload complete message so users know their changes were applied, instead of only seeing "Reloading local server...".#11673
b827893Thanks @MattieTK! - Breaks out version numbers into sortable number types for analytics loggingUpdated dependencies [
65d1850,1615fce,b2769bf,554a4df,8eede3f,6a05b1c,62fd118,a7e9f80,eac5cf7]:@cloudflare/pages-shared@0.13.96
Patch Changes
65d1850,1615fce,b2769bf,554a4df,8eede3f,6a05b1c,eac5cf7]:@cloudflare/containers-shared@0.7.0
Minor Changes
#11702
f612b46Thanks @gpanders! - Add support for trusted_user_ca_keys in WranglerYou can now configure SSH trusted user CA keys for containers. Add the following to your wrangler.toml:
This allows you to specify CA public keys that can be used to verify SSH user certificates.
#11437
9e360f6Thanks @ichernetsky-cf! - Drop deprecated containersobservability.loggingfieldPatch Changes
2a4299dThanks @gpanders! - Rename "durable_objects_active" field in ApplicationHealthInstances to "active"@cloudflare/workflows-shared@0.4.0
Minor Changes
#11648
eac5cf7Thanks @pombosilva! - Add Workflows test handlers in vitest-pool-workers to get the Workflow instance output and error:getOutput(): Returns the output of the successfully completed Workflow instance.getError(): Returns the error information of the errored Workflow instance.Example: