Minor Changes
-
#11702
f612b46Thanks @gpanders! - Add support for trusted_user_ca_keys in WranglerYou can now configure SSH trusted user CA keys for containers. Add the following to your wrangler.toml:
[[containers.trusted_user_ca_keys]] public_key = "ssh-ed25519 AAAAC3..."
This allows you to specify CA public keys that can be used to verify SSH user certificates.
-
#11620
25f6672Thanks @dario-piotrowicz! - Expose a newgetLocalWorkerdCompatibilityDateutility that allows callers to get the compatibility date of the locally installedworkerdpackage. -
#11616
fc95831Thanks @NuroDev! - Add type generation support towrangler devYou can now have your worker configuration types be automatically generated when the local Wrangler development server starts.
To use it you can either:
- Add the
--typesflag when runningwrangler dev. - Update your Wrangler configuration file to add the new
dev.generate_typesboolean property.
{ "$schema": "node_modules/wrangler/config-schema.json", "name": "example", "main": "src/index.ts", "compatibility_date": "2025-12-12", "dev": { "generate_types": true } } - Add the
-
#11620
25f6672Thanks @dario-piotrowicz! - Expose newisCompatDateutility that discerns whether a string represents a compatibility date or not
Patch Changes
-
#11737
2cfea12Thanks @NuroDev! - Fix thetriggersJSON schema default value to use valid JSON ({"crons":[]}) instead of an invalid JavaScript literal, which was causing IDE auto-completion to insert a string rather than an object. -
#11651
d123ad0Thanks @dario-piotrowicz! - Surface error in diagnostics when TOML date/time values are used invarsTOML parses unquoted date/time values like
DATE = 2024-01-01as TOML Date, Date-Time, and Time values. The config validation now surfaces an error in the diagnostics result when this type of values are encountered, with a clear message telling you to quote the value as a string, e.g.DATE = "2024-01-01". -
#11693
385ec7fThanks @vicb! - Update the signature of ParseTOML to drop the Generics.Use an explicit cast where required.