Gastón Fournier bdb763c9d5 chore!: remove deprecated default env from new installs (#10080) ... **BREAKING CHANGE**: DEFAULT_ENV changed from `default` (should not be used anymore) to `development` ## About the changes - Only delete default env if the install is fresh new. - Consider development the new default. The main consequence of this change is that the default is no longer considered `type=production` environment but also for frontend tokens due to this assumption: 724c4b78a2/src/lib/schema/api-token-schema.test.ts (L54-L59) (I believe this is mostly due to the [support for admin tokens](https://github.com/Unleash/unleash/pull/10080#discussion_r2126871567)) - `feature_toggle_update_total` metric reports `n/a` in environment and environment type as it's not environment specific		2025-06-06 12:02:21 +02:00
..
client-metrics	chore: prepare to remove default env (#10087)	2025-06-06 09:20:16 +02:00
custom	feat: custom metrics poc (#10018)	2025-05-21 16:55:30 +03:00
instance	chore!: remove deprecated default env from new installs (#10080)	2025-06-06 12:02:21 +02:00
last-seen	chore: prepare to remove default env (#10087)	2025-06-06 09:20:16 +02:00
shared	feat: custom metrics poc (#10018)	2025-05-21 16:55:30 +03:00
sizes	chore: prepare to remove default env (#10087)	2025-06-06 09:20:16 +02:00
unknown-flags	feat: Unleash v7 ESM migration (#9877)	2025-05-14 09:47:12 +02:00