Version Packages

[workers-devprod]

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.7.0

Minor Changes

• #4280 a6cd9aff Thanks @alan-agius4! - Update Angular template to use version 17

Patch Changes

• #4399 789491bd Thanks @petebacondarwin! - ci: move the Angular framework out of the C3 e2e test quarantine.

• #4242 a1c9f43f Thanks @dependabot! - C3: Bumped nuxi from 3.9.0 to 3.9.1

• #4275 e4aff81a Thanks @dependabot! - C3: Bumped create-astro from 4.3.0 to 4.4.1

• #4288 b7d91bb5 Thanks @dependabot! - C3: Bumped create-qwik from 1.2.14 to 1.2.15

• #4313 18612851 Thanks @dependabot! - C3: Bumped gatsby from 5.12.8 to 5.12.9

• #4316 3caa7860 Thanks @dependabot! - C3: Bumped create-remix from 2.1.0 to 2.2.0

• #4317 db8b5fe5 Thanks @dependabot! - C3: Bumped create-docusaurus from 2.4.3 to 3.0.0

• #4334 bde0a1bd Thanks @dependabot! - C3: Bumped create-qwik from 1.2.15 to 1.2.16

• #4335 c1223c53 Thanks @dependabot! - C3: Bumped create-solid from 0.3.8 to 0.3.9

• #4346 71eff285 Thanks @dependabot! - C3: Bumped create-qwik from 1.2.16 to 1.2.17

• #4431 c0d70bf5 Thanks @dependabot! - C3: Bumped create-astro from 4.4.1 to 4.5.1

• #4311 35be4594 Thanks @jculvey! - Changes c3 to use npx for running framework creation tools when it is invoked with yarn. This is
  needed since yarn can't yarn create some-package@some-particular-version.

• #4226 5810f815 Thanks @jculvey! - Relax empty directory check. Directories containing certain common config files and/or files created by an ide will be exempt from the pre-flight check

• #4249 b18a2c0f Thanks @dario-piotrowicz! - correct error message for unrecognized application type

• #4403 cb8ec90e Thanks @petebacondarwin! - test: fix C3 e2e tests for Angular

• #4249 b18a2c0f Thanks @dario-piotrowicz! - improve help message by adding more detailed descriptions about the various CLI options
  also let the user know that more information is available in the Cloudflare docs

• #4339 33bd75dc Thanks @alan-agius4! - Remove redundant polyfills from the Angular template

• #4279 2526794f Thanks @dnasdw! - fix: use a valid compatibility date for the scheduled worker ts template

miniflare@3.20231030.0

Minor Changes

• #4324 16cc2e92 Thanks @penalosa! - Update to latest workerd@1.20231030.0

• #4322 8a25b7fb Thanks @dario-piotrowicz! - add unsafeEvalBinding option

  Add option to leverage the newly introduced UnsafeEval workerd binding API,
  such API is used to evaluate javascript code at runtime via the provided eval and newFunction methods.

  The API, for security reasons (as per the workers docs), is not to be use in production but it is intended for local purposes only such as local testing.

  To use the binding you need to specify a string value for the unsafeEvalBinding, such will be the name of the UnsafeEval bindings that will be made available in the workerd runtime.

  For example the following code shows how to set the binding with the UNSAFE_EVAL name and evaluate the 1+1 string:

  const mf = new Miniflare({
  	log,
  	modules: true,
  	script: `
        export default {
            fetch(req, env, ctx) {
                const two = env.UNSAFE_EVAL.eval('1+1');
                return new Response('two = ' + two); // returns 'two = 2'
            }
        }
    `,
  	unsafeEvalBinding: "UNSAFE_EVAL",
  });

Patch Changes

• #4397 4f8b3420 Thanks @mrbbot! - fix: reject Miniflare#ready promise if Miniflare#dispose() called while waiting

• #4428 3637d97a Thanks @mrbbot! - fix: add miniflare bin entry

  Miniflare 3 doesn't include a CLI anymore, but should log a useful error stating this when running npx miniflare. We had a script for this, but it wasn't correctly hooked up. 🤦 This change makes sure the required bin entry exists.

• #4321 29a59d4e Thanks @mrbbot! - fix: ensure Mutex doesn't report itself as drained if locked

  Previously, Miniflare's Mutex implementation would report itself as drained
  if there were no waiters, regardless of the locked state. This bug meant that
  if you called but didn't await Miniflare#setOptions(), future calls to
  Miniflare#dispatchFetch() (or any other asynchronous Miniflare method)
  wouldn't wait for the options update to apply and the runtime to restart before
  sending requests. This change ensures we wait until the mutex is unlocked before
  reporting it as drained.

• #4307 7fbe1937 Thanks @jspspike! - Only output ipv4 addresses when starting

• #4400 76787861 Thanks @mrbbot! - fix: cleanup temporary directory after shutting down workerd

  Previously on exit, Miniflare would attempt to remove its temporary directory
  before shutting down workerd. This could lead to EBUSY errors on Windows.
  This change ensures we shutdown workerd before removing the directory.
  Since we can only clean up on a best effort basis when exiting, it also catches
  any errors thrown when removing the directory, in case the runtime doesn't
  shutdown fast enough.

@cloudflare/pages-shared@0.11.0

Minor Changes

• #4051 4578d647 Thanks @taoky! - fix: remove extension name check when generating response

  Current regex logic to check whether a pathname is a file (has file extension) is causing trouble for some websites, and now \${pathname}/index.html is always checked before returning notFound().

Patch Changes

• Updated dependencies [4f8b3420, 16cc2e92, 3637d97a, 29a59d4e, 7fbe1937, 76787861, 8a25b7fb]:
  • miniflare@3.20231030.0

wrangler@3.16.0

Minor Changes

• #4347 102e15f9 Thanks @Skye-31! - Feat(unstable_dev): Provide an option for unstable_dev to perform the check that prompts users to update wrangler, defaulting to false. This will prevent unstable_dev from sending a request to NPM on startup to determine whether it needs to be updated.

• #4179 dd270d00 Thanks @matthewdavidrodgers! - Simplify secret:bulk api via script settings

  Firing PUTs to the secret api in parallel has never been a great solution - each request independently needs to lock the script, so running in parallel is at best just as bad as running serially.

  Luckily, we have the script settings PATCH api now, which can update the settings for a script (including secret bindings) at once, which means we don't need any parallelization. However this api doesn't work with a partial list of bindings, so we have to fetch the current bindings and merge in with the new secrets before PATCHing. We can however just omit the value of the binding (i.e. only provide the name and type) which instructs the config service to inherit the existing value, which simplifies this as well. Note that we don't use the bindings in your current wrangler.toml, as you could be in a draft state, and it makes sense as a user that a bulk secrets update won't update anything else. Instead, we use script settings api again to fetch the current state of your bindings.

  This simplified implementation means the operation can only fail or succeed, rather than succeeding in updating some secrets but failing for others. In order to not introduce breaking changes for logging output, the language around "${x} secrets were updated" or "${x} secrets failed" is kept, even if it doesn't make much sense anymore.

Patch Changes

• #4402 baa76e77 Thanks @rozenmd! - This PR adds a fetch handler that uses page, assuming result_info provided by the endpoint contains page, per_page, and total

  This is needed as the existing fetchListResult handler for fetching potentially paginated results doesn't work for endpoints that don't implement cursor.

  Fixes 🐛 BUG: wrangler login only lists the first 20 accounts #4349

• #4337 6c8f41f8 Thanks @Skye-31! - Improve the error message when a script isn't exported a Durable Object class

  Previously, wrangler would error with a message like Uncaught TypeError: Class extends value undefined is not a constructor or null. This improves that messaging to be more understandable to users.

• #4307 7fbe1937 Thanks @jspspike! - Change local dev server default ip to * instead of 0.0.0.0. This will cause the dev server to listen on both ipv4 and ipv6 interfaces

• #4222 f867e01c Thanks @tmthecoder! - Support for hyperdrive bindings in local wrangler dev

• #4149 7e05f38e Thanks @jspspike! - Fixed issue with tail not using proxy

• #4219 0453b447 Thanks @maxwellpeterson! - Allows uploads with both cron triggers and smart placement enabled

• #4437 05b1bbd2 Thanks @jspspike! - Change dev registry and inspector server to listen on 127.0.0.1 instead of all interfaces

• Updated dependencies [4f8b3420, 16cc2e92, 3637d97a, 29a59d4e, 7fbe1937, 76787861, 8a25b7fb]:

  • miniflare@3.20231030.0

[codecov]

Codecov Report

Merging #4291 (03c3880) into main (2be0f3f) will increase coverage by 0.03%.
The diff coverage is n/a.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4291      +/-   ##
==========================================
+ Coverage   75.46%   75.50%   +0.03%     
==========================================
  Files         225      225              
  Lines       12478    12478              
  Branches     3239     3239              
==========================================
+ Hits         9417     9421       +4     
+ Misses       3061     3057       -4     

see 3 files with indirect coverage changes

[github-actions]

A wrangler prerelease is available for testing. You can install this latest build in your project with:

npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/6896356992/npm-package-wrangler-4291

You can reference the automatically updated head of this PR with:

npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/prs/6896356992/npm-package-wrangler-4291

Or you can use npx with this latest build directly:

npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/6896356992/npm-package-wrangler-4291 dev path/to/script.js

Additional artifacts:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/6896356992/npm-package-miniflare-4291

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/6896356992/npm-package-cloudflare-pages-shared-4291

Note that these links will no longer work once the GitHub Actions artifact expires.

---

wrangler@3.16.0 includes the following runtime dependencies:

Package	Constraint	Resolved
miniflare	workspace:*	3.20231030.0
workerd	1.20231030.0	1.20231030.0
workerd --version	1.20231030.0	2023-10-30

|

Please ensure constraints are pinned, and miniflare/workerd minor versions match.