Between last week’s v2.5.0 release (November 13), the v2.5.1 update on November 19, and v2.6.0 on November 20, we expanded OpenCI across pull request feedback, iOS Simulator E2E testing, and release-driven deployments. The workflow SDK is now at openci_workflow 0.5.3, and we also published the simulator BLE client plugin openci_virtual_ble 0.1.0.
Highlights
- Faster pull request feedback: Automatic PR comments summarize CI failures with links to the failing lines. Finished macOS jobs can be retried from the dashboard, and web preview comments now display their expiry.
- iOS Simulator E2E in Dart: Boot and dispose clean simulators, pass secrets safely to Patrol tests, and test Bluetooth LE exchanges across two simulators on one Mac.
- Automated releases and publishing: Trigger workflows on published GitHub Releases with
CITrigger.release(), deploy Firebase Functions, and publish Dart packages topub.dev. - Expanded Dart & Flutter SDK: Typed execution context (
ci.context),dart.runBuildRunner(),dart.analyze(),dart.test(),FlutterVersionpresets, andfirebase.jsonHosting config loading. - Team & runner improvements: Connect individual repositories with Write access, view monthly Cloud CI spend above the build list, and run on 4 vCPU default build VMs.
Catch PR failures faster and retry in place
Failure summaries with links to the failing lines
When a pull request workflow fails or times out, OpenCI extracts errors from the failed step and posts a summary directly in the PR conversation. Recognized flutter analyze, dart analyze, and compiler diagnostics appear in a table linking directly to the affected file and line number at the tested commit, so you do not have to dig through full build logs first.
Repeat failures update the same comment instead of adding noise. Once a subsequent run passes, the comment switches to a resolved state and folds the previous errors away. Example PR comment
One-click job retries and more reliable PR checkouts
For a transient failure, open the job details in the dashboard and select Retry job. Completed macOS jobs can be queued again on the exact same saved revision. While queued, you can still read the previous run’s logs; once the retry starts, the view switches to the live run and creates a new GitHub Check. PR #3959
PR checkouts now reverify the base branch and PR head, using GitHub’s test merge commit when it is current and falling back to a local merge inside the build VM when GitHub is still catching up. Conflicts fail cleanly at checkout, and the exact tested merge commit is recorded in the log. Retargeting a PR and immediately force-pushing also no longer lets an older webhook interrupt the latest build plan. PR #3962 · PR #3992
Typed execution context and expiring web previews
ci.context exposes a sealed PullRequestContext, PushContext, or LocalContext, making it straightforward to branch between PR previews, production deploys, and local runs with a standard Dart switch. Firebase Hosting’s deploy() and deployPreview() can also read your public directory, ignore patterns, static routing, and response headers directly from firebaseConfigPath: 'firebase.json'—without installing Node.js or the Firebase CLI.
deployPreview() now returns a FirebaseHostingPreview containing both the serving URL and the actual UTC expiresAt returned by Firebase. Pass both to postQrCode() to include the expiration time in the PR comment:
switch (ci.context) {
case PullRequestContext(:final number):
final preview = await ci.firebaseHosting.deployPreview(
siteId: 'my-hosting-site',
channelId: 'pr-$number',
expiresIn: const Duration(days: 7),
firebaseConfigPath: 'firebase.json',
serviceAccountJsonBase64:
Secrets.firebaseHostingServiceAccountJsonBase64.value,
);
await ci.pullRequest.postQrCode(
url: preview.url,
expiresAt: preview.expiresAt,
);
case PushContext(branch: 'main'):
await ci.firebaseHosting.deploy(
siteId: 'my-hosting-site',
firebaseConfigPath: 'firebase.json',
serviceAccountJsonBase64:
Secrets.firebaseHostingServiceAccountJsonBase64.value,
);
case PushContext() || LocalContext():
break;
}Pass lang: PostQrCodeLang.ja to postQrCode() if you want the comment in Japanese. This website’s own PR previews and production deploys run on this exact pattern. Website workflow
Test iOS apps with Patrol — from sign-in to two-device BLE
Boot a clean simulator and run Patrol tests
launchIosSimulator() creates a fresh iOS Simulator (defaulting to an iPhone 17 Pro on the newest compatible installed runtime), waits until boot completes, and returns its UDID. Calling simulator.dispose() inside a finally block ensures the device is shut down and removed even when a test fails.
patrol.test() runs Patrol using your project’s resolved patrol_cli package. Pass generated Secret references via env to inject test credentials safely through a temporary --dart-define-from-file (deleted automatically when the run finishes), then read them in your test under their original keys with const String.fromEnvironment(...).
final simulator = await ci.launchIosSimulator(
name: 'App Patrol',
);
try {
await ci.patrol.test(
dir: 'apps/mobile',
device: simulator.id,
targets: ['patrol_test/login_test.dart'],
env: [
Secrets.testAccountEmail,
Secrets.testAccountPassword,
],
);
} finally {
await simulator.dispose();
}The v0.1.9 macOS base image comes with Patrol CLI 4.9.0 preinstalled. OpenCI’s own dashboard app uses this workflow to boot a fresh simulator on every run and verify app launch, Firebase sign-in, and team loading end to end. Dashboard Patrol workflow
Test Bluetooth LE between two simulators
Automated testing for Bluetooth Low Energy (BLE) peer-to-peer flows usually requires two physical phones and a radio setup that is hard to maintain in CI. In v2.6.0, OpenCI can boot two iOS Simulators on the same Mac alongside two virtual Bumble GATT devices on the host, bridging GATT reads and acknowledged writes over loopback WebSockets.
ci.patrol.testWithVirtualBle() builds your Patrol target once, installs it on two fresh simulators, waits for peer B to publish its characteristic before launching peer A, and cleans up both simulators and the virtual radio when finished. Per-device logs, XCTest result bundles, and optional app JSON evidence (A.json and B.json) are saved to the returned output directory.
await ci.patrol.testWithVirtualBle(
dir: 'apps/mobile',
target: 'patrol_test/pairing_test.dart',
bundleId: 'com.example.app',
serviceUuid: 'BE110001-5D9F-4810-8692-47717E010001',
characteristicUuid: 'BE110002-5D9F-4810-8692-47717E010001',
resultJsonFile: 'ble-result.json',
);We also published the companion Flutter simulator plugin openci_virtual_ble 0.1.0 on pub.dev (flutter pub add --dev openci_virtual_ble). Apps that implement their BLE layer directly in Swift can import openci_virtual_ble and use VirtualBleConnection under #if DEBUG && targetEnvironment(simulator). For custom harnesses, the lower-level ci.startVirtualBle() session API is also available. Two-simulator Flutter example
This setup is already running in real-world app development. @aqhayami adopted OpenCI and virtual BLE for issho, running multi-simulator Bluetooth pairing E2E tests in CI:
“They also set up an E2E test that verifies Bluetooth pairing across multiple simulators. Looking forward to putting it to heavy use.” (translated from Japanese)
Ship apps, Firebase Functions, and Dart packages from releases
Trigger on GitHub Releases and deploy Firebase Functions
CITrigger.release(tag: 'v*') starts a workflow only when a matching GitHub Release (including published prereleases) is published. Draft saves and plain tag pushes do not trigger it. OpenCI resolves the tag to its exact commit, reads the workflow from that commit, and checks out that same commit—keeping day-to-day branch pushes separate from release pipelines. Enable Release events and Contents read permission on the GitHub App to use it. Triggers guide
For backend deployments, ci.firebase.functions.deploy() (SDK 0.5.3) invokes the installed Firebase CLI with a Base64-encoded service account key written to a temporary ADC file. It stays isolated from any local Firebase login state and always removes temporary credentials in finally. Omit codebase to deploy every Functions codebase in your config.
final ci = await OpenCI.init(
workflowName: 'Release Functions',
flutterVersion: FlutterVersion.v3_47_8.value,
ciTriggers: [CITrigger.release(tag: 'v*')],
);
await ci.firebase.functions.deploy(
projectId: 'my-firebase-project',
codebase: 'api',
firebaseConfigPath: 'firebase/firebase.json',
serviceAccountJsonBase64:
Secrets.firebaseServiceAccountJsonBase64.value,
);Automate pub.dev publishing and end-to-end releases
Package authors can now publish directly from Dart workflows with ci.dart.publishToPubDev(). It authenticates with a Google service account ID token—no gcloud installation required—keeps temporary pub credentials isolated and redacted from logs, and cleans them up on completion. Setting skipIfPublished: true makes reruns safe when a version is already live on pub.dev.
await ci.dart.publishToPubDev(
serviceAccountJsonBase64:
Secrets.pubDevServiceAccountJsonBase64.value,
skipIfPublished: true,
);OpenCI now runs its own release pipeline on these features. Publishing a GitHub Release builds and distributes Dashboard Shorebird releases to TestFlight and Google Play internal testing, and tests and deploys our TypeScript Firebase Functions and Dart workflow planner from the tagged commit. Merges to develop handle Shorebird patch delivery and publish openci_workflow to pub.dev after passing the two-simulator BLE checks. SDK publishing workflow · Functions CD workflow
Expanded Dart and Flutter workflow helpers
Across versions 0.3.0 through 0.5.3, openci_workflow gained typed helpers for common Dart and Flutter steps. dart.test() now accepts a paths list to run targeted test files, and Flutter jobs can enforce lockfiles with flutter.pubGet(enforceLockfile: true) before running flutter.staticAnalysis(noPub: true).
const pkg = 'packages/my_package';
await ci.dart.runBuildRunner(dir: pkg);
await ci.dart.analyze(dir: pkg, fatalInfos: true);
await ci.dart.test(dir: pkg, paths: ['test/core_test.dart']);
const app = 'apps/mobile';
await ci.flutter.pubGet(dir: app, enforceLockfile: true);
await ci.flutter.staticAnalysis(dir: app, noPub: true);You can also pass FlutterVersion.v3_44_8.value or FlutterVersion.v3_47_8.value to OpenCI.init(flutterVersion: ...) with full planner support. See the workflow guide for more examples.
Team management, spend visibility, and build runners
- Connect repositories with Write access: Once the GitHub App is installed, team members with Write, Maintain, or Admin access to a repository can connect that individual repository to an OpenCI team—no Organization Owner role required. Different repositories under one organization installation can be assigned to different OpenCI teams. PR #3950
- Monthly CI spend in the build list: The web dashboard now shows the selected Cloud team’s estimated month-to-date CI spend (tax-inclusive JPY) above the build list, with in-place refresh and a direct link to billing details. PR #3989
- Google sign-up and additional teams: New dashboard registrations now go through Continue with Google, automatically checking team membership and resuming setup if an earlier attempt was interrupted. Existing email/password accounts continue to sign in as before, and users can add extra teams from Settings → Team → Create team. PR #3969 · PR #3924
- 4 vCPU default VMs and updated macOS base image: Orchard build VMs now allocate 4 vCPUs by default (with M1 Mac workers capped at one VM for stability), and the
v0.1.9macOS base image ships with Patrol CLI 4.9.0 preinstalled. PR #3978 · PR #3958
Upgrade notes
When upgrading openci_workflow from 0.2.9 or earlier to 0.5.3, note three breaking changes:
firebaseHosting.deployPreview()return type (0.4.0): ReturnsFirebaseHostingPreviewinstead ofUri. Usepreview.urlandpreview.expiresAt. Productiondeploy()still returnsUri.CITrigger.releasecase (0.5.0):CITriggernow has a third union case. Add thereleasebranch to any exhaustiveswitch,when, ormaponCITrigger.- Removal of
OpenCI.go(0.3.0): The removal of Go helpers previously noted in v2.5.0 source changes is now included in the published pub.dev package.
GitHub Release v2.6.0 · Changes since v2.5.1 · Full week since v2.5.0 · openci_workflow 0.5.3
Cover photo by Quinn Battick on Unsplash.
RELEASE NOTES