desktop-release
Desktop Regular Release
Perform a regular desktop release from the dev branch.
This workflow is now file-driven:
apps/desktop/changelog/next.mdis the human-edited changelog draft.apps/desktop/release-plan.jsonis the human-edited release intent.pnpm --dir apps/desktop bumpapplies both inputs, writesapps/desktop/release.json, resetsapps/desktop/release-plan.json, bumps the version, createsrelease/desktop/{NEW_VERSION}, pushes it, and opens the PR.
Important notes:
mainHashis still regenerated automatically, but it is not the OTA compatibility switch anymore. Do not use it as the release decision point.runtimeVersioninapps/desktop/package.jsonis the desktop OTA compatibility key.apps/desktop/scripts/apply-release-config.impl.tswrites it during bump.- This skill covers the normal
buildandotadesktop release flow. - Do not recommend or write any other mode. The current implementation only supports
buildandota.
Pre-flight checks
More from rssnext/folo
installing-mobile-preview-builds
Builds and installs the iOS preview build for apps/mobile using EAS local build and devicectl. Use when the user asks to install a preview/internal iOS build on a connected iPhone for production-like testing.
20update-deps
Update all dependencies across frontend and backend projects. Reads changelogs for breaking changes, checks affected code, runs tests, and provides a summary. Use when updating npm dependencies across the monorepo.
19mobile-self-test
Self-test a mobile feature change or bug fix after implementation in `apps/mobile`. Use this whenever the user asks to verify a mobile change, run simulator acceptance, smoke-test a mobile PR, or provide screenshot proof for a mobile fix. This skill decides between prod vs local API mode, starts the local follow-server when needed, builds a release app, uses Maestro only to bootstrap registration for non-auth work, then switches to screenshot-driven visual validation and returns screenshot evidence.
4mobile-release
Use when preparing a mobile release from the dev branch and deciding whether changes should ship through the app stores or through the OTA pipeline before creating the release PR to mobile-main.
3mobile-e2e
Run apps/mobile Maestro end-to-end tests in this repo. Use when an agent needs to validate mobile auth flows on iOS Simulator or Android Emulator. Current maintained coverage is register, sign out, and sign in.
3