Skip to content

Version Packages #10042

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

Merged
merged 1 commit into from
Jul 24, 2025
Merged

Version Packages #10042

merged 1 commit into from
Jul 24, 2025

Conversation

workers-devprod
Copy link
Contributor

@workers-devprod workers-devprod commented Jul 22, 2025

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

[email protected]

Minor Changes

[email protected]

Minor Changes

  • #10016 c5b291d Thanks @emily-shen! - Interactively handle wrangler deploys that are probably assets-only, where there is no config file and flags are incorrect or missing.

    For example:

    npx wrangler deploy ./public will now ask if you meant to deploy a folder of assets only, ask for a name, set the compat date and then ask whether to write your choices out to wrangler.json for subsequent deployments.

    npx wrangler deploy --assets=./public will now ask for a name, set the compat date and then ask whether to write your choices out to wrangler.json for subsequent deployments.

    In non-interactive contexts, Wrangler will error as it currently does.

  • #9971 19794bf Thanks @edmundhung! - Improved script source display on the pretty error screen

Patch Changes

  • #9800 3d4f946 Thanks @helloimalastair! - remove banner from r2 getobject in pipe mode

  • #9910 7245101 Thanks @dario-piotrowicz! - make sure that the ready-on message is printed after the appropriate runtime controller is ready

    fix the fact that when starting a local (or remote) dev session the log saying Ready on http://localhost:xxxx could be displayed before the runtime is actually ready to handle requests (this is quite noticeable when locally running dev sessions with containers, where the ready message currently gets displayed before the container images building/pulling process)

  • #10031 823cba8 Thanks @vicb! - wrangler and vite-plugin now depend upon the latest version of unenv-preset

  • #10032 154acf7 Thanks @dario-piotrowicz! - add support for containers in wrangler multiworker dev

    currently when running wrangler dev with different workers (meaning that the -c|--config flag is used multiple times) containers are not being included, meaning that trying to interact with them at runtime would not work and cause errors instead. The changes here address the above making wrangler correctly detect and wire up the containers.

  • #9988 7fb0bfd Thanks @penalosa! - Correctly label mtls remote bindings warning

  • Updated dependencies [823cba8, 19794bf, 059a39e]:

[email protected]

Patch Changes

  • #10027 26186a5 Thanks @dependabot! - chore: update dependencies of "create-cloudflare" package

    The following dependency versions have been updated:

    Dependency From To
    create-react-router 7.6.3 7.7.0

@cloudflare/[email protected]

Patch Changes

@cloudflare/[email protected]

Patch Changes

  • #10031 823cba8 Thanks @vicb! - wrangler and vite-plugin now depend upon the latest version of unenv-preset

@cloudflare/[email protected]

Patch Changes

@cloudflare/[email protected]

Patch Changes

@workers-devprod workers-devprod requested review from a team as code owners July 22, 2025 15:57
@workers-devprod workers-devprod force-pushed the changeset-release/main branch from 8ba8bf7 to f2c4402 Compare July 22, 2025 15:57
Copy link

pkg-pr-new bot commented Jul 22, 2025

create-cloudflare

npm i https://pkg.pr.new/create-cloudflare@10042

@cloudflare/kv-asset-handler

npm i https://pkg.pr.new/@cloudflare/kv-asset-handler@10042

miniflare

npm i https://pkg.pr.new/miniflare@10042

@cloudflare/pages-shared

npm i https://pkg.pr.new/@cloudflare/pages-shared@10042

@cloudflare/unenv-preset

npm i https://pkg.pr.new/@cloudflare/unenv-preset@10042

@cloudflare/vite-plugin

npm i https://pkg.pr.new/@cloudflare/vite-plugin@10042

@cloudflare/vitest-pool-workers

npm i https://pkg.pr.new/@cloudflare/vitest-pool-workers@10042

@cloudflare/workers-editor-shared

npm i https://pkg.pr.new/@cloudflare/workers-editor-shared@10042

wrangler

npm i https://pkg.pr.new/wrangler@10042

commit: 1cd9af6

@workers-devprod workers-devprod force-pushed the changeset-release/main branch 4 times, most recently from 219875c to 3f84cd9 Compare July 23, 2025 12:52
@workers-devprod workers-devprod requested a review from a team as a code owner July 23, 2025 12:52
@workers-devprod workers-devprod force-pushed the changeset-release/main branch 6 times, most recently from d567de5 to 9f868a2 Compare July 23, 2025 16:12
@workers-devprod workers-devprod force-pushed the changeset-release/main branch from 9f868a2 to 1cd9af6 Compare July 23, 2025 16:18
@emily-shen emily-shen merged commit e424eb4 into main Jul 24, 2025
33 checks passed
@emily-shen emily-shen deleted the changeset-release/main branch July 24, 2025 12:56
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