CI operations
Pin GitHub Actions Without Forgetting Their Update Path
Verify action revisions, permissions and runtime downloads when pinning GitHub Actions. Maintain tested updates instead of treating immutable code as safe.
CASCADE JOURNAL
Mobile CI/CD, release engineering and product updates. Practical reading for the path from repository to release.
Filtered articles
Clear search and filtersCI operations
Verify action revisions, permissions and runtime downloads when pinning GitHub Actions. Maintain tested updates instead of treating immutable code as safe.
CI operations
Keep fork pull-request validation useful without signing secrets. Separate trusted release execution and avoid privileged workflows running untrusted code.
CI operations
Audit Flutter SDK, package and native-output caches separately. Measure restore cost, validate clean builds and preserve contribution trust boundaries.
Release observability
Diagnose unreadable Flutter Crashlytics reports by frame type, release identity, matching symbols and upload destination. Validate with safe test evidence.
CI operations
Estimate mobile CI cost from actual jobs, runner rates, retries and storage. Use a transparent worksheet and separate portable checks from iOS release work.
CI operations
Migrate off GitHub macOS 14 runner labels before retirement. Audit architecture, Xcode, dependencies and release outputs rather than changing one label.
Product Updates
Meet CascadeCI: configure Flutter releases, build with GitHub Actions and follow supported Google Play and App Store Connect status in one dashboard.