Systems | Development | Analytics | API | Testing

Apple didn't announce the M5 Pro at WWDC, and the M4 Pro Mac Mini industry shortage isn't going anywhere either. Neither should affect your CI. Apple pulled the base model from its store and discontinued the 32GB config. What's still available ships in weeks with some configs months out. Resellers are asking $979 for $599 machines and Tim Cook confirmed the constraints will last several more months.

Last year, Nathan Hillyer's iOS platform engineering team at ForeFlight had self-hosted Mac hardware in their office, two engineers keeping them alive, and a codebase with over 2 million lines of Objective-C, Swift, and C++. Every Xcode update was a fire drill. Every capacity spike during a merge meant somebody was physically racking hardware in the Austin office. ForeFlight didn't want a new CI system. They wanted to stop being a data centre.

There is a shift happening in a previously quiet corner of the open source community. You may have experienced this in your own Android builds with an HTTP 429 ("Too Many Requests") error during dependency resolution from Maven Central. Over a period of a few days in late April to early May 2026, a subset of Bitrise users experienced these errors. Here's what happened, what we did about it, and what it means for you.

When Substack first launched in 2017, the company set out to give writers a better business model, built on subscriptions and direct relationships with readers. Since then, Substack has expanded into multi-format publishing across text, audio, and video, while building powerful tools for community and discovery, for creators, writers, and thinkers of all kinds.

A critical bug is live in production. Your fix is ready. And now your team is staring at a potential multi-day wait for app store review. This is exactly what over-the-air (OTA) updates are designed to solve. Tools like Expo EAS Update, CodePush, Shorebird, Revopush or Stallion make it easy to push updates directly to users’ devices. But OTA updates don't bypass app store rules, they operate within boundaries that both Apple and Google have defined.

Running real integration tests for iOS projects is one of those problems that sounds straightforward until you're actually in it. The core tension: your backend runs on Linux, your iOS app can only build on Apple hardware. The two worlds don't meet naturally. Most teams end up mocking server responses in their mobile tests to isolate components without relying on backend services.

You asked Claude to generate a bitrise.yml. It came back clean: right steps, reasonable workflow names, valid YAML. You almost merged it. Then you noticed it’s using before_run instead of step bundles. There are no version locks on steps. The triggers are structured in a format Bitrise deprecated months ago. It’s a valid config, but it would never pass code review. The quality of an agent's interaction with your CI/CD comes down to two things: what it can do and what it knows.

Bitrise Build Hub is a vertically integrated mobile CI/CD infrastructure layer that drops into GitHub Actions with one line of YAML. GitHub Actions runs your CI, but its Mac runners are holding your mobile builds back. Limited M1/M2 hardware, stale Xcode, no cache co-location, no macOS uptime SLA. The infrastructure wasn't built for mobile. Build Hub was. Build Hub upgrades the runner layer underneath.

An outdated build environment can slow down your team, introduce security risks, and cause hard-to-debug issues. With our upgraded Linux stacks, you get a faster, more secure, and fully maintained build environment: so your team can focus on shipping great apps, rather than managing infrastructure.

React Native teams ship fast. App store reviews do not. Today, CodePush officially launched on Bitrise, giving React Native teams the ability to deliver JavaScript and asset updates directly to users in minutes, without waiting for App Store or Play Store approval.