Version Packages

[github-actions]

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

wrangler@0.0.29

Patch Changes

• #897 d0801b7 Thanks @threepointone! - polish: tweak the message when .dev.vars is used

  This tweaks the mssage when a .dev.vars file is used so that it doesn't imply that the user has to copy the values from it into their wrangler.toml.

• #880 aad1418 Thanks @GregBrimble! - fix: Stop unnecessarily amalgamating duplicate headers in Pages Functions

  Previously, set-cookie multiple headers would be combined because of unexpected behavior in the spec.

• #892 b08676a Thanks @GregBrimble! - fix: Adds the leading slash to Pages deployment manifests that the API expects, and fixes manifest generation on Windows machines.

• #852 6283ad5 Thanks @JacobMGEvans! - feat: non-TTY check for required variables
  Added a check in non-TTY environments for account_id, CLOUDFLARE_ACCOUNT_ID and CLOUDFLARE_API_TOKEN. If account_id exists in wrangler.toml
  then CLOUDFLARE_ACCOUNT_ID is not needed in non-TTY scope. The CLOUDFLARE_API_TOKEN is necessary in non-TTY scope and will always error if missing.

  resolves Throw an error if running inside github actions without CLOUDFLARE_API_TOKEN #827

• #893 5bf17ca Thanks @petebacondarwin! - fix: remove bold font from additional lines of warnings and errors

  Previously, when a warning or error was logged, the entire message
  was formatted in bold font. This change makes only the first line of
  the message bold, and the rest is formatted with a normal font.

• #894 57c1354 Thanks @threepointone! - polish: s/DO NOT USE THIS/ Ignored

  Followup to polish: s/DEPRECATION/Deprecation #888, this replaces some more scary capitals with a more chill word.

• #893 5bf17ca Thanks @petebacondarwin! - fix: add bold to the Deprecated warning title

• #882 1ad7570 Thanks @petebacondarwin! - feat: add support for reading build time env variables from a .env file

  This change will automatically load up a .env file, if found, and apply its
  values to the current environment. An example would be to provide a specific
  CLOUDFLARE_ACCOUNT_ID value.

  Related to Support .env via miniflare #190

• #887 2bb4d30 Thanks @threepointone! - polish: accept Enter as a valid key in confirm dialogs

  Instead of logging "Unrecognised input" when hitting return/enter in a confirm dialog, we should accept it as a confirmation. This patch also makes the default choice "y" bold in the dialog.

• #891 bae5ba4 Thanks @GregBrimble! - feat: Adds interactive prompts for the 'wrangler pages publish' and related commands.

  Additionally, those commands now read from node_modules/.cache/wrangler/pages.json to persist users' account IDs and project names.

• #888 b77aa38 Thanks @threepointone! - polish: s/DEPRECATION/Deprecation

  This removes the scary uppercase from DEPRECATION warnings. It also moves the service environment usage warning into diagnostics instead of logging it directly.

• #879 f694313 Thanks @petebacondarwin! - feat: read vars overrides from a local file for wrangler dev

  The vars bindings can be specified in the wrangler.toml configuration file.
  But "secret" vars are usually only provided at the server -
  either by creating them in the Dashboard UI, or using the wrangler secret command.

  It is useful during development, to provide these types of variable locally.
  When running wrangler dev we will look for a file called .dev.vars, situated
  next to the wrangler.toml file (or in the current working directory if there is no
  wrangler.toml). Any values in this file, formatted like a dotenv file, will add to
  or override vars bindings provided in the wrangler.toml.

  Related to Support .env via miniflare #190

jest-environment-wrangler@0.0.29