Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Version Packages #5134

Merged
merged 1 commit into from
Mar 5, 2024
Merged

Version Packages #5134

merged 1 commit into from
Mar 5, 2024

Conversation

workers-devprod
Copy link
Contributor

@workers-devprod workers-devprod commented Mar 1, 2024

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

wrangler@3.31.0

Minor Changes

Patch Changes

  • #5132 82a3f94 Thanks @mrbbot! - fix: switch default logging level of unstable_dev() to warn

    When running unstable_dev() in its default "test mode", the logging level was set to none. This meant any Worker startup errors or helpful warnings wouldn't be shown. This change switches the default to warn. To restore the previous behaviour, include logLevel: "none" in your options object:

    const worker = await unstable_dev("path/to/script.js", {
    	logLevel: "none",
    });
  • #5128 d27e2a7 Thanks @taylorlee! - fix: Add legacy_env support to experimental versions upload command.

  • #5087 a5231de Thanks @dario-piotrowicz! - fix: make wrangler types always generate a d.ts file for module workers

    Currently if a config file doesn't define any binding nor module, running
    wrangler types against such file would not produce a d.ts file.

    Producing a d.ts file can however still be beneficial as it would define a correct
    env interface (even if empty) that can be expanded/referenced by user code (this can
    be particularly convenient for scaffolding tools that may want to always generate an
    env interface).

    Example:
    Before wrangler types --env-interface MyEnv run with an empty wrangler.toml file
    would not generate any file, after these change it would instead generate a file with
    the following content:

    interface MyEnv {
    }
    
  • #5138 3dd9089 Thanks @G4brym! - fix: ensure Workers-AI local mode fetcher returns headers to client worker

  • Updated dependencies [42bcc72, 42bcc72]:

    • miniflare@3.20240223.1

create-cloudflare@2.13.1

Patch Changes

  • #5097 9d1d11c Thanks @dependabot! - chore: Bumped create-hono from 0.4.0 to 0.5.0

  • #5121 fd2f153 Thanks @dependabot! - chore: Bumped @angular/create from 17.2.1 to 17.2.2

  • #5122 b4f7ad8 Thanks @dependabot! - chore: Bumped create-remix from 2.7.2 to 2.8.0

  • #5135 8935526 Thanks @dario-piotrowicz! - fix: update solid preview and deploy scripts to be aligned with the rest of the frameworks

  • #5129 23074c7 Thanks @dario-piotrowicz! - fix: make sure that all C3 projects include in their .gitignore the wrangler files

    Previously only the worker templates included in their .gitignore the wrangler files (those being .dev.vars and .wrangler). Make sure to instead include such files in the .gitignore files of all the templates including the full stack ones.

  • #5135 8935526 Thanks @dario-piotrowicz! - fix: update solid C3 template to write an app.config.(js/ts) file instead of vite.config.(js/ts)

miniflare@3.20240223.1

Patch Changes

  • #5133 42bcc72 Thanks @mrbbot! - fix: ensure internals can access workerd when starting on non-local host

    Previously, if Miniflare was configured to start on a host that wasn't 127.0.0.1, ::1, *, ::, or 0.0.0.0, calls to Miniflare API methods relying on the magic proxy (e.g. getKVNamespace(), getWorker(), etc.) would fail. This change ensures workerd is always accessible to Miniflare's internals. This also fixes wrangler dev when using local network address such as 192.168.0.10 with the --ip flag.

  • #5133 42bcc72 Thanks @mrbbot! - fix: ensure IPv6 addresses can be used as hosts

    Previously, if Miniflare was configured to start on an IPv6 host, it could crash. This change ensures IPv6 addresses are handled correctly. This also fixes wrangler dev when using IPv6 addresses such as ::1 with the --ip flag.

@cloudflare/pages-shared@0.11.16

Patch Changes

@cloudflare/vitest-pool-workers@0.0.6

Patch Changes

@workers-devprod workers-devprod requested review from a team as code owners March 1, 2024 12:41
Copy link
Contributor

github-actions bot commented Mar 1, 2024

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/8160951748/npm-package-wrangler-5134

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

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

Or you can use npx with this latest build directly:

npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/8160951748/npm-package-wrangler-5134 dev path/to/script.js
Additional artifacts:
npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/8160951748/npm-package-create-cloudflare-5134 --no-auto-update
npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/8160951748/npm-package-cloudflare-kv-asset-handler-5134
npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/8160951748/npm-package-miniflare-5134
npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/8160951748/npm-package-cloudflare-pages-shared-5134
npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/8160951748/npm-package-cloudflare-vitest-pool-workers-5134

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


wrangler@3.31.0 includes the following runtime dependencies:

Package Constraint Resolved
miniflare workspace:* 3.20240223.1
workerd 1.20240223.1 1.20240223.1
workerd --version 1.20240223.1 2024-02-23

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

Copy link

codecov bot commented Mar 1, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 70.33%. Comparing base (0a5e211) to head (4aed8e7).

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main    #5134      +/-   ##
==========================================
+ Coverage   70.31%   70.33%   +0.01%     
==========================================
  Files         298      298              
  Lines       15551    15551              
  Branches     4001     4001              
==========================================
+ Hits        10935    10938       +3     
+ Misses       4616     4613       -3     

see 5 files with indirect coverage changes

@workers-devprod workers-devprod force-pushed the changeset-release/main branch 4 times, most recently from db4036a to 3764799 Compare March 4, 2024 11:06
@workers-devprod workers-devprod requested a review from a team as a code owner March 4, 2024 11:06
@workers-devprod workers-devprod force-pushed the changeset-release/main branch 14 times, most recently from 46bd344 to 49369d9 Compare March 5, 2024 14:50
@lrapoport-cf lrapoport-cf merged commit b53e0bd into main Mar 5, 2024
28 checks passed
@lrapoport-cf lrapoport-cf deleted the changeset-release/main branch March 5, 2024 18:28
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.

3 participants