Systems | Development | Analytics | API | Testing

That's Nathan Hillyer, Director of Engineering at ForeFlight, on what happened after his team started running their GitHub Actions workflows on Bitrise Build Hub. Until last month, trying that for yourself meant talking to sales first. That’s fine for a 300-person engineering org evaluating a CI overhaul, but it made no sense for the two-pizza team that just wants to know whether changing one line of YAML will meaningfully speed up their Xcode builds. That's fixed.

At Bitrise, we continually invest in security best practices to ensure that our customers' data stays safe and secure. As part of this ongoing effort, we are pleased to announce that we have successfully completed our 2026 SOC 2 Type II assessment, with no exceptions recorded in the final report. The report covers the period from July 1, 2025 to June 30, 2026 and is valid until June 30, 2027.

Namespace, Avrea, and Blacksmith are among the fastest GitHub Actions runner providers on the market right now. According to Avrea's August 2026 benchmarks, they all score within about 1% of each other on raw CPU. The same benchmark shows warm builds (populated cache) beating GitHub's default cold start (cache disabled) by anywhere from 5x to more than 140x, depending on the project.

Count how many times you’ve proudly submitted a new PR only for CI to fail for the most mundane and annoying reasons: While these lint rules are useful and important to enforce, would it be possible to just…not have to deal with them? Enter auto-fixing CI, the concept of self-healing PRs and CI workflows, without any human (or agent) interaction: The key detail that enables all of this to work: modern linters can apply trivial and mechanical fixes to most lint violations.

Most AI coding tools run in a Linux container somewhere. Codespaces is Linux. Copilot’s coding agent works in an ephemeral, Actions-powered Linux environment. Nearly every agent framework assumes a container that spins up in seconds. None of them can build your iOS app, or have build cache to speed up the builds, or have simulators that can run tests that you can view.

Apple announced the M6 and M5 Pro on August 25, 2026, both inside the redesigned Mac mini. Bitrise Build Hub will be the first GitHub Actions runner alternative to add them to the fleet. That means your builds run on the newest Apple silicon before any other GitHub Actions runner can offer it. That's not a one-off. We've shipped new runners fast on every Apple silicon generation since M1 all the way up to M4 Pro, and M5 Pro and M6 are next.

The fundamentals of React Native over-the-air updates shouldn't sit behind a paid tier. Today we're shipping three additions to Bitrise CodePush: delta updates that help significantly reduce the size of your updates, CodePush code signing so you can secure every package you push to your users’ devices, and a dedicated Bitrise CI Step that publishes updates straight from your workflow. All three are available to every CodePush user, including everyone on the free plan.

The Configuration YAML view in the Bitrise Workflow Editor now reads your entire bitrise.yml, and tells you while you type whether it's correct for your project. That means real-time validation, autocomplete, hover docs, and go-to-definition/references for anyone who edits bitrise.yml by hand. No install, no setup, available on every plan down to Hobby.

If your builds on Bitrise target the Xcode 15.x stacks, you must switch to a supported stack before September 16, 2026.