fix(cli): report production usage data only for released builds

[kanoru3101]

What/Why/How?

Our own builds and CI runs showed up in usage data as real users. Two fixes:

• Only a real release reports env: production now. Snapshots and local builds report development.
• Our CI runs no longer send telemetry at all — including the Docker smoke checks, which were sending it even with REDOCLY_TELEMETRY: off in the workflow, because containers don't see that variable.

Reference

Follow-up to #2976.

Testing

npm run compile                      → env:"development"
BUILD_ENV=production npm run compile → env:"production"

Verified in Docker: the build arg reaches RUN, and -e REDOCLY_TELEMETRY forwards the value into containers.

Check yourself

• This PR follows the contributing guide
• All new/updated code is covered by tests
• Core code changed? - Tested with other Redocly products (internal contributions only)
• New package installed? - Tested in different environments (browser/node)
• Documentation update has been considered

Security

• The security impact of the change has been considered
• Code follows company security practices and guidelines

---

Note

Low Risk
Changes affect build-time constants and CI/Docker env wiring for telemetry labeling, not runtime auth or data handling for end users.

Overview
Stops internal CI and non-release builds from polluting usage telemetry as production traffic.

The CLI esbuild step no longer hardcodes REDOCLY_CLI_BUILD_ENV to production; it now bakes in BUILD_ENV at compile time, defaulting to development when unset. The release workflow sets BUILD_ENV=production for npm publish, and Docker Hub builds pass BUILD_ENV=production via a new Dockerfile ARG and build-args.

CI telemetry is tightened: release workflow sets workflow-wide REDOCLY_TELEMETRY: 'off', and Docker smoke steps in release and smoke workflows use a redocly_docker helper that forwards -e REDOCLY_TELEMETRY into containers (so workflow env vars actually apply inside Docker).

^{Reviewed by Cursor Bugbot for commit f2ed1c5. Bugbot is set up for automated code reviews on this repo. Configure here.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: f2ed1c5

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	78.57% (🎯 77%)	13966 / 17775
🔵	Statements	78.35% (🎯 77%)	15058 / 19218
🔵	Functions	82.31% (🎯 81%)	2877 / 3495
🔵	Branches	71.63% (🎯 71%)	10377 / 14486

File Coverage

No changed files found.

Generated in workflow #11601 for commit f2ed1c5 by the Vitest Coverage Report Action

[github-actions]

Performance Benchmark (Lower is Faster)

CLI Version	Bundle	Lint	Check Config
cli-latest	▓ 1.00x ± 0.01	▓ 1.00x (Fastest)	▓ 1.00x (Fastest)
cli-next	▓ 1.00x (Fastest)	▓ 1.01x ± 0.01	▓ 1.00x ± 0.01

[github-actions]

📦 A new experimental 🧪 version v0.0.0-snapshot.1788270600 of Redocly CLI has been published for testing.

Install with NPM:

npm install @redocly/cli@0.0.0-snapshot.1788270600

⚠️ Note: This is a development build and may contain unstable features.