Skip to content

ci: engine-bump automation (RFC 0022 item 2) - #84

Open
willwade wants to merge 4 commits into
mainfrom
feat/engine-bump-automation
Open

willwade wants to merge 4 commits into
mainfrom
feat/engine-bump-automation

Conversation

@willwade

@willwade willwade commented Nov 7, 2026

Copy link
Copy Markdown
Contributor

Governance#57 item 2: weekly workflow opens a bump-DasherCore PR (with engine changelog) whenever the pin falls behind the newest engine tag. Merge-when-green becomes the whole engine-update procedure. Can be tested immediately via workflow_dispatch.

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>
…behind (RFC 0022 item 2)

Weekly + on-demand: compares the submodule pin to the newest DasherCore
v* tag and, when behind, opens a PR bumping the pin with the engine
changelog in the body. Green CI = merge; adaptation work rides the PR.
Same-repo GITHUB_TOKEN only — no org app, no PAT. The only per-repo
line is SUBMODULE (third_party/DasherCore here).

Signed-off-by: will wade <willwade@gmail.com>
Configuration fails if the pinned DasherCore's DASHER_CAPI_VERSION
(dash.h) is below the declared requirement. 'Can I bump the engine?'
becomes a build check; the engine-bump PR's green CI now proves API
compatibility too.

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

willwade commented Nov 7, 2026

Copy link
Copy Markdown
Contributor Author

Added the RFC 0022 item 3 CAPI gate to this PR's branch (same feature family): configuration now fails if the pinned engine's C-API level is below the declared minimum — green CI on an engine-bump PR doubles as the compatibility proof.

…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