Docs changelog
Subscribe to RSS
This page tracks documentation updates: new guides, updated procedures, and changes reflecting new or updated Bitrise features.
2026 Q4Click to copy link
Cloud authentication with OIDC in RDE sessionsClick to copy link
You can now get an OIDC identity token inside a Remote Dev Environment session and use it to authenticate with AWS and Google Cloud without storing long-lived credentials. The new guide covers both providers, and the OIDC overview describes the session subject format. See Cloud authentication with OIDC.
MCP server splits Release Management tool groupsClick to copy link
You can now enable only part of the Release Management tools in the Bitrise MCP server with the release-management-app and release-management-build-distribution groups, next to release-management-code-push. The release-management group still enables all of them. See Tools.
MCP server adds a build test results toolClick to copy link
The Bitrise MCP server now has a get_build_test_results tool that returns the test suites and test cases of a finished build, optionally only the failed ones. The step status tool also reports why a Step failed or was skipped. See Tools.
Antigravity CLI replaces Gemini CLI as an MCP clientClick to copy link
The Bitrise MCP and AI pages now list Google Antigravity CLI instead of Gemini CLI as a supported MCP client. See Bitrise MCP server.
Email notifications before access tokens expireClick to copy link
When you create a personal access token or a Workspace API token, you can now opt in to an email 30 and 7 days before it expires (7 days only for tokens valid for a month or less). The option is on by default. See Personal access tokens and Workspace API token.
GitHub App clone token is valid for one hourClick to copy link
The GitHub App integration guide now states that the clone token is valid for one hour, that GitHub sets this limit, and that time a build spends on hold or in the queue counts towards it. See GitHub App integration.
Bitrise MCP server in the Cursor MarketplaceClick to copy link
You can now install the Bitrise MCP server in Cursor with one click from the Cursor Marketplace, then sign in through your browser the first time a tool runs. See Install Bitrise MCP Server in Cursor.
MCP server tools carry behavior annotationsClick to copy link
Every Bitrise MCP server tool now declares whether it is read-only, destructive, or idempotent, and whether it reaches beyond your Bitrise account or workspace. See Tools.
2026 Q3Click to copy link
MCP server returns structured outputClick to copy link
Every Bitrise MCP server tool now advertises an output schema and returns its result as structured content alongside the text. See Tools.
MCP server expands tester group toolsClick to copy link
The Bitrise MCP server tools can now create tester groups and CodePush deployments together with an app, add workspace members as internal testers, and list potential testers before a group exists. See Tools.
Custom roles docs for Enterprise workspacesClick to copy link
Enterprise workspaces can now create custom roles with specific permission sets, and the docs cover creating and editing roles, the full permissions reference, and an FAQ. See Custom roles overview.
MCP server adds Insights toolsClick to copy link
The Bitrise MCP server now exposes build and test metrics from Bitrise Insights as tools, covering totals, time series, and flaky test tracking. Requires a paid Insights plan. See Bitrise MCP tools.
Workspace invitations can be rate-limitedClick to copy link
Invitations sent from Workspaces on non-paid plans may be rate-limited. See Workspace collaboration.
Product subscriptions can now be canceled independentlyClick to copy link
Each product (Bitrise CI, Build Cache, Release Management, and so on) has its own independently cancellable subscription, and add-ons can be canceled on their own too. The docs now walk through the updated Plan & Billing cancellation flow. See Workspace billing and invoicing.
Bitrise MCP server drops self-registration toolsClick to copy link
The register and verify_registration tools, along with the registration API group, are no longer part of the Bitrise MCP server. See Bitrise MCP tools.
2026 Q2Click to copy link
Agent onboarding guide updated with OAuth flowClick to copy link
The onboarding guide for AI agents now covers the full OAuth sign-in flow in detail: how your agent triggers browser authorization, creating an account during sign-in, email confirmation for password-based accounts, and troubleshooting steps for common issues.
Entra ID SCIM provisioning guideClick to copy link
You can now set up automatic user and group provisioning for your Bitrise workspace using Microsoft Entra ID SCIM. The guide covers generating SCIM credentials, configuring Entra ID, attribute mapping, group and deprovisioning behavior, and migrating existing workspace members. See Entra ID SCIM.
AI agent onboarding tip added to sign-up pageClick to copy link
The Signing up for Bitrise page now includes a tip pointing AI agents to the dedicated onboarding runbook, which covers how to create a Bitrise account and connect everything directly from an agent session without a website visit.
GitHub App integration: event subscriptions clarifiedClick to copy link
The GitHub App integration page now has an Event subscriptions section explaining that the Bitrise GitHub App subscribes to push, pull_request, and issue_comment events via GitHub's app installation mechanism, not through repo-level webhooks. The section also warns that any existing manual webhooks pointing to hooks.bitrise.io must be removed after switching to the GitHub App to avoid duplicate builds.
Bitrise MCP: new registration tools and API groupClick to copy link
The Bitrise MCP server now includes a registration API group with two unauthenticated tools — register and verify_registration — that let an AI agent onboard a brand-new Bitrise user without a token. The agent sends a one-time password to the user's email via register, then calls verify_registration with the OTP to receive a personal access token. These tools are most useful with the remote (HTTP) MCP server. See Bitrise MCP tools for the full reference.
Bitrise MCP: install guides added for six toolsClick to copy link
Step-by-step install guides for the Bitrise MCP server are now available for VS Code, Cursor, Claude, Windsurf, Kiro, Gemini CLI, and other Copilot-compatible IDEs. Each guide covers how to configure the MCP server and authenticate with your Bitrise token. See Bitrise MCP to get started.
Bitrise MCP server: OAuth is now the primary authentication methodClick to copy link
The Bitrise MCP server now uses OAuth as the primary authentication method. See Bitrise MCP for the updated setup steps.
2026 Q1Click to copy link
M4 machine type added to build machine docsClick to copy link
The Build machine types page now lists the M4 machine type alongside the existing M4 Pro, M2 Pro, and M1 options, with region availability for each.
New guide: Endpoint Detection and Response (EDR) on BitriseClick to copy link
A new page under Integrations explains how Bitrise uses Endpoint Detection and Response (EDR) as part of its corporate security program, and clarifies that EDR agents are not deployed on Bitrise-hosted CI runners.
OIDC for AWS guide updatedClick to copy link
The OIDC for AWS guide has been updated with additional clarifications on configuration and usage.
<head> <meta name="robots" content="noindex, follow" /> </head>