Fix telemetry in release builds (#41695)

Conrad Irwin created 2 days ago

This was inadvertently broken in v0.211.1-pre when we rewrote the
release build

Release Notes:

- N/A

Change summary

.github/workflows/release.yml                | 6 ++++++
tooling/xtask/src/tasks/workflows/release.rs | 5 +++++
2 files changed, 11 insertions(+)

Detailed changes

.github/workflows/release.yml

@@ -1,6 +1,12 @@
 # Generated from xtask::workflows::release
 # Rebuild with `cargo xtask workflows`.
 name: release
+env:
+  CARGO_TERM_COLOR: always
+  CARGO_INCREMENTAL: '0'
+  RUST_BACKTRACE: '1'
+  ZED_CLIENT_CHECKSUM_SEED: ${{ secrets.ZED_CLIENT_CHECKSUM_SEED }}
+  ZED_MINIDUMP_ENDPOINT: ${{ secrets.ZED_SENTRY_MINIDUMP_ENDPOINT }}
 on:
   push:
     tags:

tooling/xtask/src/tasks/workflows/release.rs

@@ -30,6 +30,11 @@ pub(crate) fn release() -> Workflow {
     named::workflow()
         .on(Event::default().push(Push::default().tags(vec!["v*".to_string()])))
         .concurrency(vars::one_workflow_per_non_main_branch())
+        .add_env(("CARGO_TERM_COLOR", "always"))
+        .add_env(("CARGO_INCREMENTAL", "0"))
+        .add_env(("RUST_BACKTRACE", "1"))
+        .add_env(("ZED_CLIENT_CHECKSUM_SEED", vars::ZED_CLIENT_CHECKSUM_SEED))
+        .add_env(("ZED_MINIDUMP_ENDPOINT", vars::ZED_SENTRY_MINIDUMP_ENDPOINT))
         .add_job(macos_tests.name, macos_tests.job)
         .add_job(linux_tests.name, linux_tests.job)
         .add_job(windows_tests.name, windows_tests.job)