Skip to content

feat(telemetry): engine_version default property (RFC 0022 item 4) - #83

Open
willwade wants to merge 2 commits into
mainfrom
feat/engine-version-telemetry
Open

willwade wants to merge 2 commits into
mainfrom
feat/engine-version-telemetry

Conversation

@willwade

@willwade willwade commented Nov 7, 2026

Copy link
Copy Markdown
Contributor

Governance#57 item 4: every analytics event carries the bundled DasherCore's version, derived at build time from the submodule pin (exact describe string — pin commits past a tag matter for triage). Makes engine drift visible in PostHog's version-adoption tile. Verified: build green, BuildConfig field populated.

Every event now carries the bundled DasherCore's version (git describe
of the third_party/DasherCore pin, e.g. 'v0.2.24-4-gc7899b65' — exact
pin commits matter for triage). Engine drift becomes visible in the
PostHog version-adoption tile instead of being discovered by survey.

Build-time derivation is exact here because the engine is bundled into
the APK (the pin IS what runs); the runtime dasher_get_engine_version()
call (DasherCore#109) can replace it at the next engine bump.

Signed-off-by: will wade <willwade@gmail.com>
…dules)

CI's submodule checkout carries no tags; git describe's merged stderr
became the BuildConfig value — multi-line garbage that broke the
generated Java string literal. Only a real describe shape is accepted
now; anything else degrades to 'unknown'.

Signed-off-by: will wade <willwade@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant