Wrangler Changelog
2024-04-11
3.50.0
#5587
d95450fThanks @CarmenPopoviciu! - fix:pages functions build-envshould throw error if invalid Pages config file is found#5572
65aa21cThanks @CarmenPopoviciu! - fix: fixpages function build-envto exit with code rather than throw fatal errorCurrently pages functions build-env throws a fatal error if a config file does not exit, or if it is invalid. This causes issues for the CI system. We should instead exit with a specific code, if any of those situations arises.
#5291
ce00a44Thanks @pmiguel! - feature: Added bespoke OAuth scope for Queues management.Updated dependencies [
08b4908]:
2024-04-10
3.49.0
#5549
113ac41Thanks @penalosa! - feat: Supportwrangler pages secret put|delete|list|bulk#5550
4f47f74Thanks @penalosa! - feat: Generate a JSON schema for the Wrangler package & use it in templates#5561
59591cdThanks @ocsfrank! - feat: update R2 CreateBucket action to include the storage class in the request body#5374
7999dd2Thanks @maxwellpeterson! - fix: Improvements to--init-from-dashAdds user-specified CPU limit to
wrangler.tomlif one exists. Excludesusage_modelfromwrangler.tomlin all cases, since this field is deprecated and no longer used.#5553
dcd65ddThanks @rozenmd! - fix: refactor d1’s time-travel compatibility check#5380
57d5658Thanks @GregBrimble! - fix: Respect--no-bundlewhen deploying a_worker.js/directory in Pages projects#5536
a7aa28aThanks @Cherry! - fix: resolve a regression wherewrangler pages devwould bind to port 8787 by default instead of 8788 since wrangler@3.38.0Updated dependencies [
9575a51]:
2024-04-05
3.48.0
#5429
c5561b7Thanks @ocsfrank! - R2 will introduce storage classes soon. Wrangler allows you to interact with storage classes once it is enabled on your account.Wrangler supports an
-sflag that allows the user to specify a storage class when creating a bucket, changing the default storage class of a bucket, and uploading an object.wrangler r2 bucket create ia-bucket -s InfrequentAccesswrangler r2 bucket update storage-class my-bucket -s InfrequentAccesswrangler r2 object put bucket/ia-object -s InfrequentAccess --file foo#5531
887150aThanks @penalosa! - fix: Writewrangler pages functions build-envto file rather than stdout#5526
bafbd67Thanks @rozenmd! - fix: teachwrangler d1 createabout Australia
2024-04-04
3.47.1
- Updated dependencies [
9f15ce1]:
3.47.0
- #5506
7734f80Thanks @penalosa! - feat: Add interactive prompt towrangler pages download configif an existingwrangler.tomlfile exists
3.46.0
#5282
b7ddde1Thanks @maxwellpeterson! - feature: Add source map support for WorkersAdds the
source_mapsboolean config option. When enabled, source maps included in the build output are uploaded alongside the built code modules. Uploaded source maps can then be used to remap stack traces emitted by the Workers runtime.#5215
cd03d1dThanks @GregBrimble! - feature: support named entrypoints in service bindingsThis change allows service bindings to bind to a named export of another Worker. As an example, consider the following Worker named
bound:import { WorkerEntrypoint } from "cloudflare:workers";export class EntrypointA extends WorkerEntrypoint {fetch(request) {return new Response("Hello from entrypoint A!");}}export const entrypointB: ExportedHandler = {fetch(request, env, ctx) {return new Response("Hello from entrypoint B!");}};export default <ExportedHandler>{fetch(request, env, ctx) {return new Response("Hello from the default entrypoint!");}};Up until now, you could only bind to the
defaultentrypoint. With this change, you can bind toEntrypointAorentrypointBtoo using the newentrypointoption:[[services]]binding = "SERVICE"service = "bound"entrypoint = "EntrypointA"To bind to named entrypoints with
wrangler pages dev, use the#character:$ wrangler pages dev --service=SERVICE=bound#EntrypointA#5215
cd03d1dThanks @GregBrimble! - fix: ensure requesturlandcfproperties preserved across service bindingsPreviously, Wrangler could rewrite
urlandcfproperties when sending requests via service bindings or Durable Object stubs. To match production behaviour, this change ensures these properties are preserved.
2024-04-03
3.45.0
#5377
5d68744Thanks @CarmenPopoviciu! - feat: Addwrangler.tomlsupport inwrangler pages deployAs we are adding
wrangler.tomlsupport for Pages, we want to ensure thatwrangler pages deployworks with a configuration file.#5471
489b9c5Thanks @zebp! - feature: Add version-id filter for Worker tailing to filter logs by scriptVersion in a gradual deploymentThis allows users to only get logs in a gradual deployment if you are troubleshooting issues specific to one deployment. Example:
npx wrangler tail --version-id 72d3f357-4e52-47c5-8805-90be978c403f#5462
68faf67Thanks @OilyLime! - revert: Removes support for private networking Hyperdrive configs, pending more work to support the feature. Non-breaking change since the feature wasn’t yet supported.#5494
a232ccfThanks @penalosa! - fix: Swallow parsing errors when a pages config file is required.#5484
e7f8dc3Thanks @ichernetsky-cf! - feature: support Cloudchamber deployment labels#5434
bf9dca8Thanks @OilyLime! - bugfix: Fix passing Hyperdrive caching options to backend#5403
5d6d521Thanks @oliy! - fix: wrangler dev –local support for ratelimitsUpdated dependencies [
940ad89]:
2024-04-02
3.44.0
#5461
f69e562Thanks @mattdeboard! - feature: Add command for fetching R2 Event Notification configurations for a given bucketThis allows users to see the entire event notification configuration – i.e. every rule for every configured queue – for a single bucket with a single request.
This change also improves messaging of console output when creating a new bucket notification.
#5480
0cce21fThanks @penalosa! - fix: Ensure url & node:url export URL (aliased to globalThis.URL) in node_compat mode#5472
02a1091Thanks @penalosa! - fix: Expose more info fromwrangler pages functions build-env