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 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
@cloudflare/[email protected]
Patch Changes
773cca3,773cca3,2e8eb24,93c4c26,48853a6,2e8eb24]:@cloudflare/[email protected]
Patch Changes
#10162
5bd0a19Thanks @emily-shen! - fix: stop containers breaking vitest-pool-workersTesting interactions with containers is still currently unsupported.
#10130
773cca3Thanks @dario-piotrowicz! - fix the potentially specified environment not being taken into account for remote bindingsUpdated dependencies [
773cca3,773cca3,2e8eb24,93c4c26,48853a6,2e8eb24]:[email protected]
Patch Changes
#10130
773cca3Thanks @dario-piotrowicz! - updatemaybeStartOrUpdateRemoteProxySessionconfig argument (to allow callers to specify an environment)Before this change
maybeStartOrUpdateRemoteProxySessioncould be called with either the path to a wrangler config file or the configuration of a worker. The former override however did not allow the caller to specify an environment, so themaybeStartOrUpdateRemoteProxySessionAPI has been updated so that in the wrangler config case an object (with the path and a potential environment) needs to be passed instead.For example, before callers could invoke the function in the following way
note that there is no way to tell the function what environment to use when parsing the wrangle configuration.
Now callers will instead call the function in the following way:
note that now a target environment can be specified.
#10130
773cca3Thanks @dario-piotrowicz! - fixgetPlatformProxynot taking into account the potentially specified environment for remote bindings#10122
2e8eb24Thanks @dario-piotrowicz! - fixstartWorkernot respectingauthoptions for remote bindingsfix
startWorkercurrently not taking into account theauthfieldthat can be provided as part of the
devoptions when used in conjunctionwith remote bindings
example:
Given the following
wranglerwill now use the provided<ACCOUNT_ID>and<API_TOKEN>to integrate withthe remote AI binding instead of requiring the user to authenticate.
#10209
93c4c26Thanks @devin-ai-integration! - fix: strip ANSI escape codes from log files to improve readability and parsing#9774
48853a6Thanks @nikitassharma! - Validate container configuration against account limits in wrangler to give early feedback to the user#10122
2e8eb24Thanks @dario-piotrowicz! - fix incorrect TypeScript type for AI binding in thestartWorkerAPI[email protected]
Minor Changes
b9d3174Thanks @devin-ai-integration! - Add GitHub issue security analysis feature to detect and alert on potential vulnerability reports