cloudflare/workers-sdk @cloudflare/config@0.8.0 on GitHub

#15326 9fcb1c9 Thanks @jamesopstad! - Rename the settings config schema exports to the input/output convention
SettingsSchema is now InputSettingsSchema and ParsedSettingsConfig is now ParsedInputSettingsConfig.
#15326 9fcb1c9 Thanks @jamesopstad! - Record the selected mode in the Build Output Specification top-level config.json
The mode a build was produced in is now written to .cloudflare/output/v0/config.json as a mode field, alongside the account and compliance settings.
#15318 82d11fc Thanks @jamesopstad! - Consolidate development-only binding configuration under dev
This experimental configuration now uses dev.remote for remote bindings and dev.connectionString for Hyperdrive. Miniflare's v5 binding configuration follows the same shape, and R2's local S3 credentials now share the dev object.
#15325 7f66836 Thanks @jamesopstad! - Reject conflicting destination restrictions in send-email bindings
Send-email bindings now match Wrangler validation by allowing either destinationAddress or allowedDestinationAddresses, but not both. allowedSenderAddresses remains an independent restriction that can accompany either destination mode.

#15324 ead8f69 Thanks @jamesopstad! - Fix the inferred type of ConfigExportsSchema to reserve the settings key for settings configuration
Parsed config exports now expose settings as a settings configuration while treating all other exports as Worker configurations. Validation continues to report specific errors when a settings configuration uses the wrong export name or the reserved name contains a Worker configuration, and now explains how to handle unsupported exports.
#15297 acb14d0 Thanks @jamesopstad! - Fix declaration emit for values returned by defineSettings
Projects can now export a defineSettings() result while generating TypeScript declarations without encountering TS4023.