Skip to content

[Frontend][Telemetry] appVersion is hardcoded to '0.1.0' in telemetry payloads — wire it from build config #2182

Description

@Chris0Jeky

What

frontend/taskdeck-web/src/store/telemetryStore.ts:158 hardcodes appVersion: '0.1.0', // Will be set from build config in future in every telemetry event payload. Nothing in the UI renders it, and the backend-reported product version (Taskdeck.Application.Common.ProductVersion/health/live, /health/ready, CLI version) is tag-derived and correct — but a v0.2.0 build still self-reports 0.1.0 in telemetry traces, and every future release will drift the same way.

Found by the 2026-08-29 v0.2.0 release-readiness audit (finding F-8). Not tag-blocking, not user-visible.

Acceptance

  • appVersion comes from build configuration (e.g. a Vite define fed by the release workflow's tag-derived version, with the same 0.0.0-dev fallback the backend uses) instead of a literal; do not hand-bump the literal to 0.2.0.
  • telemetryApi contract/spec updated to assert the injected value.
  • docs/platform/CONFIGURATION_REFERENCE.md or the release workflow comment records where the frontend version comes from.

Related: #1804 (backend version stamp), #1948 (truthful sidebar version stamp).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Priority IVLater maturity/deepening; revisited at horizon planning.frontendPrimary implementation impact in Vue/TypeScript UI and client runtime.tech-debtDebt cleanup or deferred engineering quality work with limited product-surface change.

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions