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
Better releases, explained.
Mobile CI/CD, release engineering and product updates. Practical reading for the path from repository to release.
Filtered articles
Clear search and filtersCI operations
Secrets Missing in Fork Pull Requests: Keep Release Credentials Out of Untrusted Builds
Keep fork pull-request validation useful without signing secrets. Separate trusted release execution and avoid privileged workflows running untrusted code.
CI operations
Flutter CI Caching: Separate SDK, Package and Native Build Caches
Audit Flutter SDK, package and native-output caches separately. Measure restore cost, validate clean builds and preserve contribution trust boundaries.
CI operations
Estimate Mobile CI Costs: Separate Linux Builds from macOS Release Work
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
GitHub’s macOS 14 Runner Retirement: Migrate the Whole Build Environment
Migrate off GitHub macOS 14 runner labels before retirement. Audit architecture, Xcode, dependencies and release outputs rather than changing one label.