# Docs changelog
Subscribe to RSS
This page tracks documentation updates: new guides, updated procedures, and changes reflecting new or updated Bitrise features.
## 2026 Q4
### Run a workspace script on every session boot {#2026-11-09-run-a-workspace-script-on-every-session-boot}
You can now set one Bash script that every Remote Dev Environment session in your workspace runs before the template's setup. The new page covers which sessions run it, the environment it runs in, and how to handle secrets. See [Workspace script](/bitrise-rde/configuration/workspace-script).
### Lifecycle hooks for Remote Dev Environment templates {#2026-11-09-lifecycle-hooks-for-remote-dev-environment-templates}
Templates can now run **On create**, **On claim** and **On restore** hooks in place of the warmup and startup scripts. The new guide explains when each hook runs and how to write one. See [Lifecycle hooks](/bitrise-rde/configuration/lifecycle-hooks).
### Maestro Test 1.1.0 retries failed flows {#2026-11-04-maestro-test-1-1-0-retries-failed-flows}
The Maestro guide now covers retrying failed flows, skipping quarantined flows, and the per-attempt outputs of Maestro Test 1.1.0. Each Configuration YAML tab now explains its Steps one by one. See [Running Maestro tests on Bitrise](/bitrise-ci/testing/running-maestro-tests-on-bitrise).
### Test reports now has its own section {#2026-11-03-test-reports-now-has-its-own-section}
The single test results page is now a Test reports section with one page per task: an overview of the Steps each framework needs, deploying test results, viewing them, and test attachments. See [Test reports overview](/bitrise-ci/testing/test-reports/overview).
### Cloud authentication with OIDC in RDE sessions {#2026-10-29-cloud-authentication-with-oidc-in-rde-sessions}
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](/bitrise-rde/configuration/oidc-cloud-authentication).
### MCP server splits Release Management tool groups {#2026-10-29-mcp-server-splits-release-management-tool-groups}
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](/bitrise-platform/ai/bitrise-mcp/tools).
### Get build step summaries and test results through the API {#2026-10-28-get-build-step-summaries-and-test-results-through-the-api}
The Bitrise CI API reference now covers two build endpoints: one returns the Workflows and Steps of a build with their status, timing, and failure reasons, and the other returns the test suites and test cases of a finished build. See [Get the step summary of a build](/bitrise-api/api-reference/build-log-summary).
### MCP server adds a build test results tool {#2026-10-28-mcp-server-adds-a-build-test-results-tool}
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](/bitrise-platform/ai/bitrise-mcp/tools).
### No Output Timeout in pull request builds {#2026-10-27-no-output-timeout-in-pull-request-builds}
The guide on aborting hanging Steps now explains that you must expose the `BITRISE_NO_OUTPUT_TIMEOUT` Secret to pull requests, or the function silently doesn't apply to pull request builds. It also points to the per-Step alternative for apps that can't expose Secrets. See [Detecting and aborting hanging Steps](/bitrise-ci/workflows-and-pipelines/steps/detecting-and-aborting-hanging-steps).
### SceneDelegate is the default iOS setup for CodePush {#2026-10-27-scenedelegate-is-the-default-ios-setup-for-codepush}
The CodePush setup guide now shows the iOS bundle URL change in `SceneDelegate.swift`, which apps created with React Native 0.88 or later use. A note covers apps that still initialize React Native in `AppDelegate.swift`. See [Configuring your app for CodePush](/release-management/codepush/configuring-your-app-for-codepush).
### Run Maestro tests on Bitrise {#2026-10-26-run-maestro-tests-on-bitrise}
A new guide explains how to run Maestro flows with the Maestro Test Step on Android and iOS, covering flow variables, tag filtering, and sharding across parallel Workflows. See [Running Maestro tests on Bitrise](/bitrise-ci/testing/running-maestro-tests-on-bitrise).
### Antigravity CLI replaces Gemini CLI as an MCP client {#2026-10-26-antigravity-cli-replaces-gemini-cli-as-an-mcp-client}
The Bitrise MCP and AI pages now list Google Antigravity CLI instead of Gemini CLI as a supported MCP client. See [Bitrise MCP server](/bitrise-platform/ai/bitrise-mcp).
### Release CodePush updates from CI with the Step or CLI {#2026-10-22-release-codepush-updates-from-ci-with-the-step-or-cli}
The CodePush CI guide now uses the Bitrise CodePush Publish Step or the CodePush CLI instead of manual scripts, and identifies deployments by name instead of ID. See [Releasing CodePush updates with Bitrise CI](/release-management/codepush/codepush-updates-with-bitrise-ci).
### Android release note edits are kept during rollout {#2026-10-22-android-release-note-edits-are-kept-during-rollout}
The Android release guide and the release presets page now state that a manual release note edit is kept when you change the rollout percentage later. See [Releasing your app on Google Play](/release-management/releases/managing-the-release-process/releasing-your-app-on-google-play).
### Rebuild a build through the API {#2026-10-21-rebuild-a-build-through-the-api}
The Bitrise CI API reference now includes the endpoint that rebuilds a finished build with the same parameters and Workflow, optionally with remote access enabled. See [Rebuild a build](/bitrise-api/api-reference/build-rebuild).
### Access Insights data with the Insights API {#2026-10-20-access-insights-data-with-the-insights-api}
You can now use the public, read-only Insights API to pull your build and test data into your own tools, automation, and AI agents. See [Insights API overview](/insights/insights-api-overview).
### GitHub App installation requirement for RDE {#2026-10-20-github-app-installation-requirement-for-rde}
The RDE GitHub integration guide now explains that the Bitrise GitHub App must be installed on the organization that owns the repository, and which error you see if it isn't. See [GitHub integration](/bitrise-rde/configuration/github-integration).
### Email notifications before access tokens expire {#2026-10-19-email-notifications-before-access-tokens-expire}
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](/bitrise-platform/accounts/personal-access-tokens#expiry-notification-emails) and [Workspace API token](/bitrise-platform/workspaces/workspace-api-token#expiry-notification-emails).
### Warm pools belong to the workspace {#2026-10-09-warm-pools-belong-to-the-workspace}
Warm pools are now workspace resources rather than personal ones, and the guide explains who can use a pool and who owns a session claimed from it. The UI, CLI, and API examples and the RDE API reference no longer mention an owner choice. See [Warm pools](/bitrise-rde/configuration/warm-pools).
### GitHub App clone token is valid for one hour {#2026-10-09-github-app-clone-token-is-valid-for-one-hour}
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-platform/repository-access/github-app-integration).
### Corrected CodePush upload command {#2026-10-09-corrected-codepush-upload-command}
The API example for uploading a CodePush update now uses the upload script's current variable names (`UPDATE_PATH`, with `CONNECTED_APP_ID` removed), so the command no longer fails with an empty update path. See [Creating and releasing CodePush updates](/release-management/codepush/creating-and-releasing-codepush-updates).
### Corrected CodePush CI updates guide {#2026-10-08-corrected-codepush-ci-updates-guide}
The CodePush CI updates guide no longer asks for deployment key Secrets that the Workflow never read, clears old bundles before each build, and has you set the target versions yourself with an `APP_TARGET_VERSIONS` Env Var. See [CodePush updates with Bitrise CI](/release-management/codepush/codepush-updates-with-bitrise-ci).
### Link test attachments by file name {#2026-10-08-link-test-attachments-by-file-name}
You can now link test attachments to their test cases by naming each file after its test case, with setups for Espresso, Paparazzi, Roborazzi, Detox, and Playwright. This needs the Deploy to Bitrise.io Step version 2.26.0 or newer. See [Naming attachments after their test case](/bitrise-ci/testing/test-reports/test-attachments/naming-attachments-after-test-cases).
### Bitrise MCP server in the Cursor Marketplace {#2026-10-08-bitrise-mcp-server-in-the-cursor-marketplace}
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](/bitrise-platform/ai/bitrise-mcp/installing-the-bitrise-mcp-server/install-cursor).
### Verify CodePush delta updates {#2026-10-07-verify-codepush-delta-updates}
You can now confirm that Bitrise created deltas for a CodePush update and that the SDK applied them. The guide also explains how code signing works with delta updates. See [Delta updates](/release-management/codepush/delta-updates).
### Release Management permissions page corrected {#2026-10-06-release-management-permissions-page-corrected}
The roles and permissions page now matches the permission matrix: it lists 18 previously missing actions, corrects what Release managers and Project Admins can do, and splits rows where roles differ. See [Release Management roles and permissions](/release-management/configuring-connected-apps/release-management-roles-and-permissions).
### Limit Bitrise for Jira to selected projects {#2026-10-06-limit-bitrise-for-jira-to-selected-projects}
A Jira admin can now show the **Bitrise builds** section only on issues in selected Jira projects, instead of in every project. On existing installations, the setting becomes available after an admin approves the app update. See [Bitrise for Jira app](/bitrise-ci/run-and-analyze-builds/build-data-and-troubleshooting/bitrise-for-jira-app).
### CodePush CLI shows delta generation status {#2026-10-06-codepush-cli-shows-delta-generation-status}
The `update status` command now shows whether Bitrise has finished generating deltas for an update and which earlier updates they are based on. See [Using the CodePush CLI](/release-management/codepush/codepush-cli/using-the-codepush-cli).
### MCP server tools carry behavior annotations {#2026-10-06-mcp-server-tools-carry-behavior-annotations}
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](/bitrise-platform/ai/bitrise-mcp/tools).
## 2026 Q3
### Bitrise CLI adds build trigger flags {#2026-09-30-bitrise-cli-adds-build-trigger-flags}
You can now set the stack, machine type, and license pool when you run `bitrise build trigger`, and pass `--env` values without variable expansion. The `--priority` flag now overrides the configured priority even when it's `0`. See [Managing builds with the Bitrise CLI](/bitrise-ci/bitrise-cli/managing-builds-with-the-bitrise-cli).
### Bazel Build Cache installs CLI to local bin {#2026-09-30-bazel-build-cache-installs-cli-to-local-bin}
The Bazel Build Cache setup guides now install the Bitrise Build Cache CLI into `$HOME/.local/bin` and add it to `PATH`, so Bazel finds the credential helper by name from any repository. See [Configuring the Build Cache for Bazel in GitHub Actions](/bitrise-build-cache/build-cache-for-bazel/configuring-the-build-cache-for-bazel-in-github-actions).
### CodePush supports binary diffing delta updates {#2026-09-30-codepush-supports-binary-diffing-delta-updates}
You can now opt in to binary diffing for CodePush delta updates with Bitrise CodePush SDK 10.6.0 or newer, and the guide explains how Bitrise generates deltas between updates. See [Delta updates](/release-management/codepush/delta-updates).
### MCP server returns structured output {#2026-09-30-mcp-server-returns-structured-output}
Every Bitrise MCP server tool now advertises an output schema and returns its result as structured content alongside the text. See [Tools](/bitrise-platform/ai/bitrise-mcp/tools).
### Non-Bitrise CI Build Cache uses workspace tokens {#2026-09-29-non-bitrise-ci-build-cache-uses-workspace-tokens}
The Build Cache setup guides for Gradle, Bazel, Xcode, and React Native on other CI providers now recommend a workspace API token instead of a personal access token. See [Getting started with the Build Cache](/bitrise-build-cache/getting-started-with-the-build-cache/getting-started-with-the-build-cache).
### New guides for the Bitrise CLI {#2026-09-29-new-guides-for-the-bitrise-cli}
The Bitrise CLI section now covers logging in, configuring the CLI, managing builds, and working with `bitrise.yml` from the command line. See [Authenticating with the Bitrise CLI](/bitrise-ci/bitrise-cli/authenticating-with-the-bitrise-cli).
### Create fully configured projects from the CLI {#2026-09-29-create-fully-configured-projects-from-the-cli}
The project creation guide now follows the redesigned page, where you copy a command that creates a fully configured project in your current workspace. With Bitrise CLI v3, you can also create just the project skeleton with `bitrise app create`. See [Adding a new project from a CLI](/bitrise-ci/bitrise-cli/adding-a-new-project-from-a-cli).
### Warm pools for Remote Dev Environments {#2026-09-25-warm-pools-for-remote-dev-environments}
You can now keep pre-booted Remote Dev Environment sessions ready in a warm pool, so new sessions and device preview links open in seconds. Create pools in the UI, the CLI, with an AI agent, or through the API. See [Warm pools](/bitrise-rde/configuration/warm-pools).
### Per-project Build Cache scoping {#2026-09-25-per-project-build-cache-scoping}
You can now limit the Build Cache on a machine to the projects you opt in, instead of caching every project. See [Per-project cache scoping](/bitrise-build-cache/getting-started-with-the-build-cache/per-project-cache-scoping).
### CodePush CLI documents source map options {#2026-09-25-codepush-cli-documents-source-map-options}
The CodePush CLI guide now explains where the CLI writes source maps by default and how to set a custom location with `--sourcemap-output`. See [Using the CodePush CLI](/release-management/codepush/codepush-cli/using-the-codepush-cli).
### Preview link sessions are workspace-owned {#2026-09-23-preview-link-sessions-are-workspace-owned}
Sessions opened from a device preview link now always belong to the workspace, whichever credential created the link. You find them under **Workspace sessions**, not in your personal session list. See [Device preview links](/bitrise-rde/devices/device-preview-links).
### Build Hub runners need no Build Cache token {#2026-09-22-build-hub-runners-need-no-build-cache-token}
On Bitrise Build Hub runners, the Build Cache CLI authenticates itself because the machine is already connected to your workspace. This needs Bitrise Build Cache CLI v3.10.0 or newer. See [Getting started with the Build Cache](/bitrise-build-cache/getting-started-with-the-build-cache/getting-started-with-the-build-cache).
### MCP server expands tester group tools {#2026-09-22-mcp-server-expands-tester-group-tools}
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](/bitrise-platform/ai/bitrise-mcp/tools).
### Pin builds to the latest Stable stack {#2026-09-22-pin-builds-to-the-latest-stable-stack}
You can now use the `osx-xcode-latest-stable` and `ubuntu-latest-stable` stack IDs so your builds always run on the current Stable stack. See [Setting the stack for your builds](/bitrise-ci/configure-builds/configuring-build-settings/setting-the-stack-for-your-builds#using-the-latest-stable-stack).
### Update CI docs with CLI v3 syntax {#2026-09-21-update-ci-docs-with-cli-v3-syntax}
CI documentation now shows CLI v3 command syntax, where commands like `bitrise run` are documented as `bitrise local run`. Existing commands keep working as before. See [Running your first local build with the CLI](/bitrise-ci/bitrise-cli/running-your-first-local-build-with-the-cli).
### Remote Dev Environments adds virtual devices {#2026-09-18-remote-dev-environments-adds-virtual-devices}
You can now use an iOS simulator or Android emulator on Remote Dev Environments, either through an interactive device session or a shareable device preview link. See [Virtual devices](/bitrise-rde/devices/virtual-devices).
### Fixed who can toggle pull request build approval {#2026-09-18-fixed-who-can-toggle-pull-request-build-approval}
The docs now correctly say that Edit workflows (not Approve build requests) controls who can turn the manual pull-request-approval setting on or off. Approve build requests only covers approving or declining individual builds once that setting is on. See [Approving pull request builds](/bitrise-ci/run-and-analyze-builds/starting-builds/approving-pull-request-builds).
### GitHub Actions setup guides for the Build Cache {#2026-09-18-github-actions-setup-guides-for-the-build-cache}
Each Build Cache tool (Gradle, Xcode, Bazel, React Native) now has a dedicated GitHub Actions setup guide, with runnable workflow YAML for both Build Hub runners and GitHub-hosted runners. See [Configuring the Build Cache for Gradle in GitHub Actions](/bitrise-build-cache/build-cache-for-gradle/configuring-the-build-cache-for-gradle-in-github-actions).
### Local Build Cache builds now push by default {#2026-09-17-local-build-cache-builds-now-push-by-default}
Activating the Build Cache locally for Gradle, Bazel, and React Native now pushes to the cache by default, matching CI behavior. Pull-only mode is still available as an opt-in. See [Configuring the Build Cache for Gradle in local builds](/bitrise-build-cache/build-cache-for-gradle/configuring-the-build-cache-for-gradle-in-local-builds).
### Custom roles docs for Enterprise workspaces {#2026-09-17-custom-roles-docs-for-enterprise-workspaces}
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](/bitrise-platform/workspaces/collaboration-and-permissions-in-workspaces/custom-roles/custom-roles-overview).
### Clarified runs-on label matching for Build Hub GitHub Actions pools {#2026-09-17-clarified-runs-on-label-matching-for-build-hub-github-actions-pools}
The docs now spell out that a machine pool must have every label listed in a job's `runs-on` array, not just one of them, with a worked example. See [Configuring your GitHub Actions workflow](/bitrise-build-hub/build-hub-for-github-actions/configuring-your-github-actions-workflow).
### MCP server adds Insights tools {#2026-09-15-mcp-server-adds-insights-tools}
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](/bitrise-platform/ai/bitrise-mcp/tools).
### Getting started with AI for the Build Cache {#2026-09-15-getting-started-with-ai-for-the-build-cache}
A new page gives you a ready-to-use AI prompt for setting up the Build Cache with a coding agent like Claude Code. See [Getting started with AI](/bitrise-build-cache/getting-started-with-the-build-cache/getting-started-with-ai).
### Remote Dev Environments is generally available {#2026-09-10-remote-dev-environments-is-generally-available}
Remote Dev Environments has left beta. The beta notice has been removed from the RDE documentation, and the overview now points to self-serve sign-up alongside the sales route. The RDE API is still marked experimental: endpoints and payloads can change in backwards-incompatible ways. See [Remote Dev Environments overview](/bitrise-rde/getting-started/remote-dev-environments-overview).
### Track Remote Dev Environments usage across API, CLI, MCP, and UI {#2026-09-01-track-remote-dev-environments-usage-across-api-cli-mcp-and-ui}
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](/bitrise-rde/configuration/rde-api).
### CodePush delta updates {#2026-08-31-codepush-delta-updates}
Learn what delta updates are, why they matter, and which version Bitrise currently supports. See [Delta updates](/release-management/codepush/delta-updates).
### Enable Build Cache writes for React Native on non-Bitrise CI {#2026-08-26-enable-build-cache-writes-for-react-native-on-non-bitrise-ci}
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](/bitrise-build-cache/build-cache-for-react-native/configuring-the-build-cache-for-react-native-in-non-bitrise-ci-environments).
### GitHub stacked pull requests {#2026-08-25-github-stacked-pull-requests}
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](/bitrise-ci/run-and-analyze-builds/build-triggers/about-build-triggers).
### Remote Dev Environments FAQ, and a corrected session retention model {#2026-08-24-remote-dev-environments-faq-and-a-corrected-session-retention-model}
New [Remote Dev Environments FAQ](/bitrise-rde/getting-started/rde-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](/bitrise-build-hub/infrastructure/build-stacks/stack-deprecation-and-removal-policy). [Key concepts](/bitrise-rde/getting-started/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 Collaboration {#2026-08-14-manage-remote-dev-environments-access-from-collaboration}
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](/bitrise-rde/configuration/managing-rde-access).
### Utility builds beta for Pro plans {#2026-08-06-utility-builds-beta-for-pro-plans}
Short Linux builds that run on the Linux Small machine type don't count against your build quota during the beta. See [Utility builds](/bitrise-ci/run-and-analyze-builds/utility-builds).
### Edit modular YAML in the Workflow Editor {#2026-08-05-edit-modular-yaml-in-the-workflow-editor}
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](/bitrise-ci/configure-builds/configuration-yaml/editing-a-modular-configuration-in-the-workflow-editor).
### Linux tooling steps scoped to the Docker-based image {#2026-07-30-linux-tooling-steps-scoped-to-the-docker-based-image}
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 your GitHub Actions workflow](/bitrise-build-hub/build-hub-for-github-actions/configuring-your-github-actions-workflow#enabling-linux-machines-to-access-tooling).
### Select Bazel RBE worker pools by name {#2026-07-30-select-bazel-rbe-worker-pools-by-name}
Remote Build Execution for Bazel now routes builds with a single `Pool=` execution property, instead of separate architecture and OS properties.
### CodePush SDK setup steps rewritten {#2026-07-30-codepush-sdk-setup-steps-rewritten}
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](/release-management/codepush/configuring-your-app-for-codepush).
### Bitrise CI API reference corrections {#2026-07-24-bitrise-ci-api-reference-corrections}
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 limits {#2026-07-24-configuration-yaml-reference-gains-missing-limits}
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-limited {#2026-07-24-workspace-invitations-can-be-rate-limited}
Invitations sent from Workspaces on non-paid plans may be rate-limited. See [Workspace collaboration](/bitrise-platform/workspaces/collaboration-and-permissions-in-workspaces/workspace-collaboration).
### Developing a new step guide rewritten {#2026-07-20-developing-a-new-step-guide-rewritten}
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 commands {#2026-07-14-rde-cli-docs-refreshed-to-match-current-commands}
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](/bitrise-rde/rde-options/bitrise-rde-cli).
### Building a Slack-native coding agent {#2026-07-10-building-a-slack-native-coding-agent}
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-rde/recipes/building-a-slack-native-coding-agent-recipe).
### Bitrise Desktop App for macOS {#2026-07-09-bitrise-for-mac-menu-bar-app-guide}
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](/bitrise-ci/run-and-analyze-builds/bitrise-desktop-app-for-macos).
### Product subscriptions can now be canceled independently {#2026-07-07-product-subscriptions-can-now-be-canceled-independently}
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-platform/workspaces/workspace-billing-and-invoicing).
### Bitrise MCP server drops self-registration tools {#2026-07-02-bitrise-mcp-server-drops-self-registration-tools}
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](/bitrise-platform/ai/bitrise-mcp/tools).
## 2026 Q2
### RDE API reference now available in-site {#2026-06-29-rde-api-reference-now-available-in-site}
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](/bitrise-rde-api/api-reference/bitrise-remote-dev-environments-api).
### Remote Dev Environments docs now available {#2026-06-29-remote-dev-environments-docs-now-available}
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](/bitrise-rde).
### Agent onboarding guide updated with OAuth flow {#2026-06-26-agent-onboarding-guide-updated-with-oauth-flow}
The [onboarding guide for AI agents](/bitrise-platform/ai/onboarding-for-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 guide {#2026-06-23-entra-id-scim-provisioning-guide}
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-platform/accounts/saml-sso-in-bitrise/setting-up-entra-id-scim-for-bitrise).
### Bitrise CI API reference is now interactive {#2026-06-22-bitrise-ci-api-reference-is-now-interactive}
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](/bitrise-api).
### CodePush CLI docs expanded with full reference {#2026-06-19-codepush-cli-docs-expanded-with-full-reference}
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](/release-management/codepush/codepush-cli/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](/release-management/codepush/codepush-cli/about-the-codepush-cli).
### AI agent onboarding tip added to sign-up page {#2026-06-18-ai-agent-onboarding-tip-added-to-sign-up-page}
The [Signing up for Bitrise](/bitrise-platform/getting-started/signing-up-for-bitrise) page now includes a tip pointing AI agents to the [dedicated onboarding runbook](/bitrise-platform/ai/onboarding-for-agents), 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 clarified {#2026-06-17-github-app-integration-event-subscriptions-clarified}
The [GitHub App integration](/bitrise-platform/repository-access/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 group {#2026-06-15-bitrise-mcp-new-registration-tools-and-api-group}
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](/bitrise-platform/ai/bitrise-mcp/tools) for the full reference.
### Bitrise MCP: install guides added for six tools {#2026-06-15-bitrise-mcp-install-guides-added-for-six-tools}
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](/bitrise-platform/ai/bitrise-mcp) to get started.
### Workflow Editor can now push bitrise.yml directly to the repository {#2026-06-11-workflow-editor-can-now-push-bitrise-yml-directly-to-the-repository}
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](/bitrise-ci/configure-builds/configuration-yaml/storing-an-apps-configuration-yaml) for the updated flow.
### Build Hub: Gradle dependency mirroring explained {#2026-06-10-build-hub-gradle-dependency-mirroring-explained}
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 switcher {#2026-06-09-configuration-yaml-docs-updated-for-yaml-visual-mode-switcher}
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 manager {#2026-06-08-new-guide-maven-central-repository-manager}
A new guide covering the Maven Central repository manager is now available under [Build Cache getting started](/bitrise-build-cache/getting-started-with-the-build-cache/maven-central-repository-manager). 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 method {#2026-06-08-bitrise-mcp-server-oauth-is-now-the-primary-authentication-method}
The Bitrise MCP server now uses OAuth as the primary authentication method. See [Bitrise MCP](/bitrise-platform/ai/bitrise-mcp) for the updated setup steps.
### Build distribution: custom access links for installable artifacts {#2026-05-29-build-distribution-custom-access-links-for-installable-artifacts}
In Release Management, you can now create shareable install links. See [Custom access links](/release-management/build-distribution/distributing-builds-to-testers#custom-access-link) for details.
### Modular YAML: increased file and nesting limits for GitHub users {#2026-05-28-modular-yaml-increased-file-and-nesting-limits-for-github-users}
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](/bitrise-ci/configure-builds/configuration-yaml/modular-yaml-configuration) for the updated limits.
### Python projects now supported {#2026-05-20-python-projects-now-supported}
Bitrise now detects Python projects automatically and offers default workflows. The [Default workflows](/bitrise-ci/workflows-and-pipelines/workflows/default-workflows) and [Getting started with Bitrise CI](/bitrise-ci/getting-started/getting-started) guides have been updated to include Python.
### Next.js and Flutter Web project types documented {#2026-04-20-next-js-and-flutter-web-project-types-documented}
The [Getting started with Bitrise CI](/bitrise-ci/getting-started/getting-started) guide and [Default workflows](/bitrise-ci/workflows-and-pipelines/workflows/default-workflows) page now cover Next.js (as an extension of Node.js) and Flutter Web project types.
## 2026 Q1
### M4 machine type added to build machine docs {#2026-03-30-m4-machine-type-added-to-build-machine-docs}
The [Build machine types](/bitrise-platform/infrastructure/build-machines/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 supported {#2026-03-25-ruby-projects-now-supported}
Bitrise now detects Ruby projects automatically and offers default workflows. The [Getting started with Bitrise CI](/bitrise-ci/getting-started/getting-started) guide has been updated to include Ruby.
### Pro Trial: credit card required to access the full trial {#2026-03-24-pro-trial-credit-card-required-to-access-the-full-trial}
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](/bitrise-ci/getting-started/getting-started) guide has been updated to explain this.
### New page: build artifact retention policy {#2026-03-20-new-page-build-artifact-retention-policy}
A dedicated [Build artifact retention policy](/bitrise-ci/run-and-analyze-builds/managing-build-files/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 analytics {#2026-03-10-xcode-compilation-cache-new-flag-to-disable-caching-without-disabling-analytics}
The [Xcode compilation cache FAQ](/bitrise-build-cache/build-cache-for-xcode/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.
### Build Cache: clear cache button replaces Settings dropdown {#2026-02-20-build-cache-clear-cache-button-replaces-settings-dropdown}
The [Clearing the Build Cache](/bitrise-build-cache/getting-started-with-the-build-cache/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 Bitrise {#2026-02-20-new-guide-endpoint-detection-and-response-edr-on-bitrise}
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 updated {#2026-02-13-oidc-for-aws-guide-updated}
The [OIDC for AWS](/bitrise-platform/integrations/oidc-authentication/oidc-for-aws) guide has been updated with additional clarifications on configuration and usage.
### New guide: GitHub App migration API {#2026-02-03-new-guide-github-app-migration-api}
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](/bitrise-ci/api/adding-and-managing-apps) for details.
### Tool setup: new tool versions added {#2026-01-27-tool-setup-new-tool-versions-added}
The [Configuring tool versions](/bitrise-ci/configure-builds/configuring-build-settings/configuring-tool-versions) guide has been updated with newly supported tool versions in the tool setup feature.
### Build artifact retention policy documented {#2026-01-19-build-artifact-retention-policy-documented}
The [Build artifacts](/bitrise-ci/run-and-analyze-builds/managing-build-files/build-artifacts-online) 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 explained {#2026-01-12-pipeline-rebuild-dynamic-parallel-workflows-explained}
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](/bitrise-ci/run-and-analyze-builds/build-data-and-troubleshooting/rebuilding-a-failed-build#rebuilding-a-failed-pipeline) for details.