🐛 BUG: passing an invalid compatibility_date in wrangler.toml causes env variables not to be bound

[adamdehaven]

Which Cloudflare product(s) does this pertain to?

Workers Runtime, Wrangler

What version(s) of the tool(s) are you using?

3.82.0 [Wrangler]

What version of Node are you using?

20.18.0

What operating system and version are you using?

Mac Sonoma

Describe the Bug

Observed behavior

Passing an invalid compatibility_date in a wrangler.toml (e.g. 2024-11-05 as of today) does not throw an error; however, it causes any environment variables and secrets to not be available in the deployed worker.

Expected behavior

The invalid compatibility_date should fallback to the latest valid compatibility_date, and environment variables and secrets should be properly available in the worker.

Steps to reproduce

1. Create a valid wrangler.toml with the following setting:

   compatibility_date = "2024-11-05"

2. Add an environment secret in the Cloudflare Dashboard UI, and deploy the secret
3. Deploy your worker via wrangler using the wrangler.toml and notice your environment variable is not available.

Please provide a link to a minimal reproduction

No response

Please provide any relevant error logs

No response

[irvinebroque]

Can't reproduce this with same exact steps, are you certain that is happening?

[adamdehaven]

Can't reproduce this with same exact steps, are you certain that is happening?

I’m not sure why else I’d have opened the issue…

Is there a recommended way to submit a reproduction?

[WalshyDev]

Add an environment secret in the Cloudflare Dashboard UI, and deploy the secret

Make sure this is a secret and not an environment variable. If you define an env var (not secret) within the dashboard and deploy with it not in your wrangler.toml it will be removed.

We recently updated the UI to make it clearer when you're adding a secret - can you please try this again? Make sure to select "Type" -> "Secret"

Sorry that this is confusing, hopefully the new UI helps :)

[adamdehaven]

Make sure this is a secret and not an environment variable.

Yes, it’s a secret defined in our terraform config for the worker

[penalosa]

Is there a recommended way to submit a reproduction?

Could you provide a link to a GitHub repo that demonstrates the issue?