Files

T

Claude e8c7162bc0 Move to the 1.1 series, from one place rather than three

The series a build is named for was written out three times — in the
build file and in both workflows' tag lines — so bumping it meant
changing all three and a release could be tagged one thing and built as
another. It now lives in gradle.properties as plgVersionSeries, which
the build reads when it stamps the APK and both workflows read when they
name the tag.

Set to 1.1.

versionCode is deliberately left as the CI run number alone, which is
what makes the bump safe: the run number keeps climbing across a change
of series, so 1.1 never looks like a downgrade to Android and an OTA
update is not interrupted. The series is a name for people; the run
number is what the machines compare. The updater already read only the
trailing number, and its comments now say so rather than naming 1.0.

Co-Authored-By: Claude Opus 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_019Pr6B8xDDtJJcb6WJMw7Ud

2026-08-07 15:50:30 +00:00

2.9 KiB

Raw Blame History

Working on this repo with Claude

Nothing a session does triggers CI. Dispatch it explicitly.

GitHub creates no workflow run for anything this sandbox does — pushing a branch, opening a pull request, or merging one. All of it goes through the same integration, and GitHub suppresses event-triggered runs from it. The pull request will say it was opened by the repo owner; that is only how the UI attributes it, and it does not change the suppression.

This was measured, not assumed:

Action	Result
Human pushes a Claude-authored commit (`d165e5ef`, `469c900e`)	CI runs
Session pushes `dev` / `main` (`43394b8`, `742add4`)	no run
Session opens a PR against `dev` (#1)	no run
Session calls `workflow_dispatch`	runs

workflow_dispatch works because it creates a run directly instead of relying on an event. It is the only mechanism available from a session, so every build has to be asked for by hand.

Verify before merging, without publishing

ci.yml builds, tests and lints on any ref, but its staging and publishing steps are gated on github.ref == 'refs/heads/dev'. Dispatching it on a feature branch therefore gives the full check — build, unit tests, Android lint — and publishes nothing.

So the working loop is:

Commit and push the feature branch.
Dispatch ci.yml on that branch. Wait for green. This is the real review gate, and it is the only verification that exists (see below).
Open the PR through the API and merge it there, so the change is reviewable and the merge commit is honest about what happened. Neither step builds anything.
Dispatch the target branch's workflow to actually build and publish: ci.yml on dev, release.yml on main.

Skipping step 4 leaves a branch whose head was never built and no release.

Merging is a shipping action

Both long-lived branches publish, so a merge is a release, not just an integration:

dev → ci.yml publishes a v<series>.N-dev prerelease, offered by the in-app updater to anyone on the Dev channel.
main → release.yml publishes a production release, which the updater installs for everyone on the Production channel.

Confirm before shipping to main. Note that release.yml runs assembleDebug only — no tests, no lint — so a main release is only as verified as the dev build it replays.

Gradle does not run in the sandbox

./gradlew cannot resolve the Android plugin here: the proxy blocks dl.google.com with a 403. No local build, no local test run, no local lint. A dispatched CI run is the only way to find out whether a change compiles.

A permanent fix, if you want one

The suppression is a property of the sandbox's credential, so it cannot be fixed from inside a session. Giving the environment a personal access token to push with would make pushes and PRs behave normally for everyone. Until then, the dispatch step above is the workaround.

2.9 KiB Raw Blame History