Skip to main content

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​

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 Deploying and viewing test results.

Limit Bitrise for Jira to selected projectsClick to copy link​

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.

2026 Q3Click to copy link​

Bitrise CLI adds build trigger flagsClick to copy link​

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.

New guides for the Bitrise CLIClick to copy link​

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.

Create fully configured projects from the CLIClick to copy link​

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.

Pin builds to the latest Stable stackClick to copy link​

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.

Update CI docs with CLI v3 syntaxClick to copy link​

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.

Fixed who can toggle pull request build approvalClick to copy link​

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.

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.

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.

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.

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.

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.

2026 Q2Click to copy link​

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.

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.

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.

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.

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

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.

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.

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.