メインコンテンツまでスキップ

Docs changelog

This page tracks documentation updates: new guides, updated procedures, and changes reflecting new or updated Bitrise features.

Subscribe to RSS

2026 SeptemberClick to copy link​

Track Remote Dev Environments usage across API, CLI, MCP, and UIClick to copy link​

You can now check RDE workspace usage through the REST API, the rde usage CLI command, the MCP server, or the UI. See Remote Dev Environments API.

2026 AugustClick to copy link​

CodePush delta updatesClick to copy link​

Learn what delta updates are, why they matter, and which version Bitrise currently supports. See Delta updates.

Enable Build Cache writes for React Native on non-Bitrise CIClick to copy link​

Docs now show how to pass --cache-push so a non-Bitrise CI provider can write to the Build Cache, not just read from it. See Configuring the Build Cache for React Native in non-Bitrise CI environments.

GitHub stacked pull requestsClick to copy link​

Trigger conditions and $BITRISEIO_GIT_BRANCH_DEST now explain how Bitrise handles GitHub stacked pull requests, matching against the stack's base branch. See About build triggers.

Remote Dev Environments FAQ, and a corrected session retention modelClick to copy link​

New Remote Dev Environments FAQ answers the most common questions about sessions, storage, connecting, credentials, AI coding agents, and limits.

The session retention documentation was also corrected. Terminated sessions are not cleaned up after a fixed period: a session's persistent disk is kept until you delete it, or until the stack it was created from is removed under the stack deprecation and removal policy. Key concepts now also explains that a session stays permanently tied to the stack it was created from and can't be moved to a different one.

Manage Remote Dev Environments access from CollaborationClick to copy link​

RDE is now a standalone product in workspace collaboration: grant or revoke the RDE User role for members and groups from the Collaboration page, or assign it through SCIM with rde:rde_admin. See Managing RDE access.

Utility builds beta for Pro plansClick to copy link​

Short Linux builds that run on the Linux Small machine type don't count against your build quota during the beta. See Utility builds.

Edit modular YAML in the Workflow EditorClick to copy link​

The Workflow Editor now loads every module of a configuration split with the include keyword, shows the merged result, and pushes your changes back to your repository in one step. See Editing a modular configuration in the Workflow Editor.

2026 JulyClick to copy link​

Linux tooling steps scoped to the Docker-based imageClick to copy link​

The tooling-access steps for Build Hub Linux machines apply only to the deprecated Docker-based image. If you use linux-bitvirt-2026, you can skip them. See Configuring Build Hub for GitHub Actions.

Select Bazel RBE worker pools by nameClick to copy link​

Remote Build Execution for Bazel now routes builds with a single Pool=<pool-name> execution property, instead of separate architecture and OS properties.

CodePush SDK setup steps rewrittenClick to copy link​

The React Native and Expo setup guides now match the current CodePush SDK, with the Expo instructions first. See Configuring your mobile app for CodePush.

Bitrise CI API reference correctionsClick to copy link​

The API documentation now covers the pipeline outgoing-webhook event type, the full set of app role groups, optional Android keystore parameters, and the correct build notification defaults.

Configuration YAML reference gains missing limitsClick to copy link​

The reference now documents the status_report_name and parallel limits, trigger priority, and the values should_always_run actually accepts.

Workspace invitations can be rate-limitedClick to copy link​

Invitations sent from Workspaces on non-paid plans may be rate-limited. See Workspace collaboration.

Developing a new step guide rewrittenClick to copy link​

The walkthrough for building your own Step has been rewritten, with inaccurate statements corrected and background material trimmed.

RDE CLI docs refreshed to match current commandsClick to copy link​

The RDE CLI reference now covers stack-based session creation, running commands in a session with session exec, VNC tunneling, workspace selection, and the reconnect behavior of rde claude. See Bitrise RDE CLI.

Building a Slack-native coding agentClick to copy link​

A new recipe walks through a reference architecture for a Slack-native coding agent: a locked-down orchestrator that delegates coding work to disposable Remote Dev Environments, plus an open source reference implementation you can try. See Building a Slack-native coding agent.

Bitrise Desktop App for macOSClick to copy link​

A new guide covers the Bitrise Desktop App for macOS: installing it, signing in, selecting a workspace and project, configuring filters and notifications, and troubleshooting. See Bitrise Desktop App for macOS.

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 JuneClick to copy link​

RDE API reference now available in-siteClick to copy link​

The Remote Dev Environments REST API reference is now part of docs.bitrise.io as a native interactive explorer, covering 42 endpoints across user, workspace, sessions, templates, and saved inputs. See RDE API reference.

Remote Dev Environments docs now availableClick to copy link​

Documentation for Bitrise Remote Dev Environments (RDE) is now available, covering key concepts, a quickstart, configuration options (templates, saved inputs), and the available interfaces: CLI, MCP server, UI, and VS Code plugin. See Remote Dev Environments.

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.

Bitrise CI API reference is now interactiveClick to copy link​

The Bitrise CI API reference is now available as a full interactive explorer at /en/bitrise-api, replacing the previous SwaggerUI embed. Endpoints are grouped by tag with a sidebar, and you can try requests directly from the docs. See Bitrise CI API reference.

CodePush CLI docs expanded with full referenceClick to copy link​

The CodePush CLI documentation has been expanded and restructured. A new reference page covers all commands, global flags, environment variables, and exit codes. The Using the CodePush CLI page now includes workflow examples, JSON output, and Bitrise CI integration details. The code signing page adds a directory naming warning and a React Native >= 0.61 Android setup note. See CodePush CLI.

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 and coding assistants 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.

Workflow Editor can now push bitrise.yml directly to the repositoryClick to copy link​

The Workflow Editor now supports pushing changes to a repository-stored bitrise.yml directly from the editor — either to the current branch or a new branch — without manually copying and committing. See Storing an app's configuration YAML for the updated flow.

Build Hub: Gradle dependency mirroring explainedClick to copy link​

The Build Hub documentation now includes an explanation of how Gradle dependency mirroring works, giving you a clearer picture of caching behaviour for Gradle projects running on Build Hub.

Configuration YAML docs updated for YAML/Visual mode switcherClick to copy link​

References throughout the docs have been updated to reflect the new toggle between YAML and Visual editing modes in the Workflow Editor. Where instructions previously referred to the left navigation menu, they now point to the YAML toggle at the top of the editor.

New guide: Maven Central repository managerClick to copy link​

A new guide covering the Maven Central repository manager is now available under Build Cache getting started. It explains how Bitrise's proxy cache works for Maven dependencies, covers special cases like dependency verification and custom Docker images, and documents the opt-out process.

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 MayClick to copy link​

In Release Management, you can now create shareable install links. See Custom access links for details.

Modular YAML: increased file and nesting limits for GitHub usersClick to copy link​

The modular YAML configuration guide has been updated to reflect the new, higher file count and nesting limits for GitHub users. See Modular YAML configuration for the updated limits.

Python projects now supportedClick to copy link​

Bitrise now detects Python projects automatically and offers default workflows. The Default workflows and Getting started with Bitrise CI guides have been updated to include Python.

2026 AprilClick to copy link​

Next.js and Flutter Web project types documentedClick to copy link​

The Getting started with Bitrise CI guide and Default workflows page now cover Next.js (as an extension of Node.js) and Flutter Web project types.

2026 MarchClick 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.

Ruby projects now supportedClick to copy link​

Bitrise now detects Ruby projects automatically and offers default workflows. The Getting started with Bitrise CI guide has been updated to include Ruby.

Pro Trial: credit card required to access the full trialClick to copy link​

New users now need to provide a valid credit card (which won't be charged) to access the full Pro Trial. The Getting started with Bitrise CI guide has been updated to explain this.

New page: build artifact retention policyClick to copy link​

A dedicated Build artifact retention policy page is now available, covering default retention periods by artifact type, extended retention options for enterprise customers, and the edge case around transferred projects.

Xcode compilation cache: new flag to disable caching without disabling analyticsClick to copy link​

The Xcode compilation cache FAQ now documents the --no-bitrise-build-cache flag, which lets you disable caching temporarily while keeping analytics and build history intact.

2026 FebruaryClick to copy link​

Build Cache: clear cache button replaces Settings dropdownClick to copy link​

The Clearing the Build Cache guide has been updated to reflect the current UI: the Settings dropdown was replaced by a Clear Cache button. The guide includes a new screenshot and a note that clearing the cache requires Workspace owner permissions.

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.

New guide: GitHub App migration APIClick to copy link​

A new guide explains how to use the Bitrise API to bulk-migrate projects from OAuth-based GitHub connections to the GitHub App integration, including caveats about reverting the migration. See Adding and managing apps for details.

2026 JanuaryClick to copy link​

Tool setup: new tool versions addedClick to copy link​

The Configuring tool versions guide has been updated with newly supported tool versions in the tool setup feature.

Build artifact retention policy documentedClick to copy link​

The Build artifacts page now includes a section on the artifact retention policy, covering default retention periods by artifact type and options for Enterprise customers. The policy takes effect on March 31, 2026.

Pipeline rebuild: dynamic parallel workflows explainedClick to copy link​

The guide on rebuilding failed pipelines now includes an explanation of how dynamic parallel Workflows affect rebuild options — specifically, when you can rebuild individual Workflows versus all unsuccessful ones. See Rebuilding a failed build for details.

<head> <meta name="robots" content="noindex, follow" /> </head>