* feat(mobile): ship Android as dev.orca.app and check updates by install source
Android becomes dev.orca.app, the package already live on Google Play; iOS keeps
com.stably.orca.mobile. The move screens and the "Orca (old)" label stay keyed to the old package,
so they never show in the new app.
The app asks Android who installed it. A Play install gets its updates from Play, so it runs no
GitHub check, hides "Check for updates" and points the update wall at Google Play. Any other
install checks GitHub for android-v releases; the old package keeps mobile-android-v.
* ci(mobile): release dev.orca.app to Play and publish Google's signed APK
An android-v tag (or a manual run) builds the AAB with the upload key and sends it to Play's
internal track. It then downloads the universal APK Google signed for that versionCode, fails unless
its V3.0 signer is Google's app signing key, and publishes it as the android-v GitHub pre-release.
Play and GitHub installs are the same signed app. A manual run with publish_github_release off only
validates the bundle with Play.
The orca.dev APK bump job is gone: the site builds its link from mobile-android-v, so it stays on
the last old-app APK, which sends people to the new app.
* ci: isolate real-process skill release suites
Linux and mac skill-sharing release gates hit child-readiness marker
timeouts in run 43573545467. The nested Vitest children inherit
process.env, and per-file isolation is only on for Windows unless
ORCA_VITEST_ISOLATE_EVERY_FILE is set. Reapply the reviewed 258 fix
(3ad9722af6) to both skill-suite steps. No suite, assertion or
timeout changes.
* fix(release): draft from the verified tag with default-branch metadata
Run 43573545467 got 403 "Resource not accessible by integration" because
the draft POST sent the release commit SHA as target_commitish, which
needs workflow authority GITHUB_TOKEN cannot get. The existing tag owns
source identity; target_commitish is ignored for an existing tag, so
send the default-branch name as API metadata (design B, as in
d28d414bbd), with the D1b fixes:
- An already-published release, or one published mid-preparation, now
fails instead of returning success to downstream builds.
- Peel the captured tag object ID (git/tags, git/commits) rather than
re-dereferencing the tag name; bind it to the checkout and SOURCE_SHA.
- Refuse a draft electron-builder would not select first (untagged,
bare-version shadow, other id, published, invisible), the #21835 shape.
- Re-read the tag after drafting, export the verified tag object and
commit, and re-check both immediately before publish-release undrafts.
Uses only the official GITHUB_TOKEN.
* chore(endpoints): call orca.dev for feedback, plugin lists and update notes
The site moved to orca.dev. Feedback, connection diagnostics, plugin install
stats, the plugin kill list, update nudges and the changelog feed now use
orca.dev, as do the diagnostics token URL baked into builds and the release
download mirror (downloads.orca.dev). The old hosts serve the same paths,
so released builds keep working.
Skill share links on share.orca.dev are accepted, and the mobile scanner
recognizes the orca.dev Android download code. The old hosts stay accepted.
* chore(ci): leave the release JavaScript benchmark workflow unchanged
Editing it triggers the benchmark, whose parity check currently fails on
arm64 because max-quality brotli output for the mobile page differs by
architecture. The benchmark only needs some diagnostics URL, and the old
host still serves it.
onorca.dev offers an opt-in 'mirror link' (https://downloads.onorca.dev)
next to the GitHub download for when GitHub release downloads 5xx.
Upload the onorca.dev download assets there right after each stable
desktop release and each Android release, instead of polling.
- config/scripts/release/publication/mirror-release-to-r2.sh: retrying,
resumable download from GitHub, size + sha256 check, S3 multipart
upload to R2 (no 300 MiB wrangler cap)
- release-mirror-r2.yml: reusable + manual backfill
- release-cut: run after publish-release for stable vX.Y.Z tags only
- mobile-android-release: run before bump-apk-download so the site's
mirror link never points at a missing APK (success not required)
* Keep dropped-macOS updaters on their last compatible build and explain why
Stamp minimumSystemVersion into every mac update manifest from the built
app's LSMinimumSystemVersion, and refuse to publish an ungated release.
When the updater withholds a newer release for this macOS, show a one-time
notice and say so in Settings and the update card.
* Trim the unsupported-Mac notice copy