<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Bitrise Docs changelog</title>
    <link>https://docs.bitrise.io/en/bitrise-ci/changelog</link>
    <atom:link href="https://docs.bitrise.io/changelog.xml" rel="self" type="application/rss+xml" />
    <description>A record of documentation updates on the Bitrise docs site.</description>
    <language>en</language>
    <lastBuildDate>Wed, 17 Jun 2026 00:00:00 GMT</lastBuildDate>
  <item>
    <title>GitHub App integration: event subscriptions clarified</title>
    <link>https://docs.bitrise.io/en/bitrise-ci/changelog#2026-06-17-github-app-integration-event-subscriptions-clarified</link>
    <guid isPermaLink="false">https://docs.bitrise.io/en/bitrise-ci/changelog#2026-06-17-github-app-integration-event-subscriptions-clarified</guid>
    <pubDate>Wed, 17 Jun 2026 00:00:00 GMT</pubDate>
    <description>The [GitHub App integration](/en/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&apos;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.</description>
  </item>
  <item>
    <title>Bitrise MCP: new registration tools and API group</title>
    <link>https://docs.bitrise.io/en/bitrise-ci/changelog#2026-06-15-bitrise-mcp-new-registration-tools-and-api-group</link>
    <guid isPermaLink="false">https://docs.bitrise.io/en/bitrise-ci/changelog#2026-06-15-bitrise-mcp-new-registration-tools-and-api-group</guid>
    <pubDate>Mon, 15 Jun 2026 00:00:00 GMT</pubDate>
    <description>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&apos;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](/en/bitrise-platform/ai/bitrise-mcp/tools) for the full reference.</description>
  </item>
  <item>
    <title>Bitrise MCP: install guides added for six tools</title>
    <link>https://docs.bitrise.io/en/bitrise-ci/changelog#2026-06-15-bitrise-mcp-install-guides-added-for-six-tools</link>
    <guid isPermaLink="false">https://docs.bitrise.io/en/bitrise-ci/changelog#2026-06-15-bitrise-mcp-install-guides-added-for-six-tools</guid>
    <pubDate>Mon, 15 Jun 2026 00:00:00 GMT</pubDate>
    <description>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](/en/bitrise-platform/ai/bitrise-mcp) to get started.</description>
  </item>
  <item>
    <title>Workflow Editor can now push bitrise.yml directly to the repository</title>
    <link>https://docs.bitrise.io/en/bitrise-ci/changelog#2026-06-11-workflow-editor-can-now-push-bitrise-yml-directly-to-the-repository</link>
    <guid isPermaLink="false">https://docs.bitrise.io/en/bitrise-ci/changelog#2026-06-11-workflow-editor-can-now-push-bitrise-yml-directly-to-the-repository</guid>
    <pubDate>Thu, 11 Jun 2026 00:00:00 GMT</pubDate>
    <description>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&apos;s configuration YAML](/en/bitrise-ci/configure-builds/configuration-yaml/storing-an-apps-configuration-yaml) for the updated flow.</description>
  </item>
  <item>
    <title>Build Hub: Gradle dependency mirroring explained</title>
    <link>https://docs.bitrise.io/en/bitrise-ci/changelog#2026-06-10-build-hub-gradle-dependency-mirroring-explained</link>
    <guid isPermaLink="false">https://docs.bitrise.io/en/bitrise-ci/changelog#2026-06-10-build-hub-gradle-dependency-mirroring-explained</guid>
    <pubDate>Wed, 10 Jun 2026 00:00:00 GMT</pubDate>
    <description>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.</description>
  </item>
  <item>
    <title>Configuration YAML docs updated for YAML/Visual mode switcher</title>
    <link>https://docs.bitrise.io/en/bitrise-ci/changelog#2026-06-09-configuration-yaml-docs-updated-for-yaml-visual-mode-switcher</link>
    <guid isPermaLink="false">https://docs.bitrise.io/en/bitrise-ci/changelog#2026-06-09-configuration-yaml-docs-updated-for-yaml-visual-mode-switcher</guid>
    <pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate>
    <description>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.</description>
  </item>
  <item>
    <title>New guide: Maven Central repository manager</title>
    <link>https://docs.bitrise.io/en/bitrise-ci/changelog#2026-06-08-new-guide-maven-central-repository-manager</link>
    <guid isPermaLink="false">https://docs.bitrise.io/en/bitrise-ci/changelog#2026-06-08-new-guide-maven-central-repository-manager</guid>
    <pubDate>Mon, 08 Jun 2026 00:00:00 GMT</pubDate>
    <description>A new guide covering the Maven Central repository manager is now available under [Build Cache getting started](/en/bitrise-build-cache/getting-started-with-the-build-cache/maven-central-repository-manager). It explains how Bitrise&apos;s proxy cache works for Maven dependencies, covers special cases like dependency verification and custom Docker images, and documents the opt-out process.</description>
  </item>
  <item>
    <title>Bitrise MCP server: OAuth is now the primary authentication method</title>
    <link>https://docs.bitrise.io/en/bitrise-ci/changelog#2026-06-08-bitrise-mcp-server-oauth-is-now-the-primary-authentication-method</link>
    <guid isPermaLink="false">https://docs.bitrise.io/en/bitrise-ci/changelog#2026-06-08-bitrise-mcp-server-oauth-is-now-the-primary-authentication-method</guid>
    <pubDate>Mon, 08 Jun 2026 00:00:00 GMT</pubDate>
    <description>The Bitrise MCP server now uses OAuth as the primary authentication method. See [Bitrise MCP](/en/bitrise-platform/ai/bitrise-mcp) for the updated setup steps.</description>
  </item>
  <item>
    <title>Build distribution: custom access links for installable artifacts</title>
    <link>https://docs.bitrise.io/en/bitrise-ci/changelog#2026-05-29-build-distribution-custom-access-links-for-installable-artifacts</link>
    <guid isPermaLink="false">https://docs.bitrise.io/en/bitrise-ci/changelog#2026-05-29-build-distribution-custom-access-links-for-installable-artifacts</guid>
    <pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate>
    <description>In Release Management, you can now create shareable install links. See [Custom access links](/en/release-management/build-distribution/distributing-builds-to-testers#custom-access-link) for details.</description>
  </item>
  <item>
    <title>Modular YAML: increased file and nesting limits for GitHub users</title>
    <link>https://docs.bitrise.io/en/bitrise-ci/changelog#2026-05-28-modular-yaml-increased-file-and-nesting-limits-for-github-users</link>
    <guid isPermaLink="false">https://docs.bitrise.io/en/bitrise-ci/changelog#2026-05-28-modular-yaml-increased-file-and-nesting-limits-for-github-users</guid>
    <pubDate>Thu, 28 May 2026 00:00:00 GMT</pubDate>
    <description>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](/en/bitrise-ci/configure-builds/configuration-yaml/modular-yaml-configuration) for the updated limits.</description>
  </item>
  <item>
    <title>Python projects now supported</title>
    <link>https://docs.bitrise.io/en/bitrise-ci/changelog#2026-05-20-python-projects-now-supported</link>
    <guid isPermaLink="false">https://docs.bitrise.io/en/bitrise-ci/changelog#2026-05-20-python-projects-now-supported</guid>
    <pubDate>Wed, 20 May 2026 00:00:00 GMT</pubDate>
    <description>Bitrise now detects Python projects automatically and offers default workflows. The [Default workflows](/en/bitrise-ci/workflows-and-pipelines/workflows/default-workflows) and [Getting started with web CI](/en/bitrise-ci/getting-started/quick-start-guides/getting-started-with-web-ci) guides have been updated to include Python.</description>
  </item>
  <item>
    <title>Next.js and Flutter Web project types documented</title>
    <link>https://docs.bitrise.io/en/bitrise-ci/changelog#2026-04-20-next-js-and-flutter-web-project-types-documented</link>
    <guid isPermaLink="false">https://docs.bitrise.io/en/bitrise-ci/changelog#2026-04-20-next-js-and-flutter-web-project-types-documented</guid>
    <pubDate>Mon, 20 Apr 2026 00:00:00 GMT</pubDate>
    <description>The [Getting started with web CI](/en/bitrise-ci/getting-started/quick-start-guides/getting-started-with-web-ci) guide and [Default workflows](/en/bitrise-ci/workflows-and-pipelines/workflows/default-workflows) page now cover Next.js (as an extension of Node.js) and Flutter Web project types.</description>
  </item>
  <item>
    <title>M4 machine type added to build machine docs</title>
    <link>https://docs.bitrise.io/en/bitrise-ci/changelog#2026-03-30-m4-machine-type-added-to-build-machine-docs</link>
    <guid isPermaLink="false">https://docs.bitrise.io/en/bitrise-ci/changelog#2026-03-30-m4-machine-type-added-to-build-machine-docs</guid>
    <pubDate>Mon, 30 Mar 2026 00:00:00 GMT</pubDate>
    <description>The [Build machine types](/en/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.</description>
  </item>
  <item>
    <title>Ruby projects now supported</title>
    <link>https://docs.bitrise.io/en/bitrise-ci/changelog#2026-03-25-ruby-projects-now-supported</link>
    <guid isPermaLink="false">https://docs.bitrise.io/en/bitrise-ci/changelog#2026-03-25-ruby-projects-now-supported</guid>
    <pubDate>Wed, 25 Mar 2026 00:00:00 GMT</pubDate>
    <description>Bitrise now detects Ruby projects automatically and offers default workflows. The [Getting started with web CI](/en/bitrise-ci/getting-started/quick-start-guides/getting-started-with-web-ci) guide has been updated to include Ruby.</description>
  </item>
  <item>
    <title>Pro Trial: credit card required to access the full trial</title>
    <link>https://docs.bitrise.io/en/bitrise-ci/changelog#2026-03-24-pro-trial-credit-card-required-to-access-the-full-trial</link>
    <guid isPermaLink="false">https://docs.bitrise.io/en/bitrise-ci/changelog#2026-03-24-pro-trial-credit-card-required-to-access-the-full-trial</guid>
    <pubDate>Tue, 24 Mar 2026 00:00:00 GMT</pubDate>
    <description>New users now need to provide a valid credit card (which won&apos;t be charged) to access the full Pro Trial. The [Getting started with Bitrise CI](/en/bitrise-ci/getting-started/getting-started) guide has been updated to explain this.</description>
  </item>
  <item>
    <title>New page: build artifact retention policy</title>
    <link>https://docs.bitrise.io/en/bitrise-ci/changelog#2026-03-20-new-page-build-artifact-retention-policy</link>
    <guid isPermaLink="false">https://docs.bitrise.io/en/bitrise-ci/changelog#2026-03-20-new-page-build-artifact-retention-policy</guid>
    <pubDate>Fri, 20 Mar 2026 00:00:00 GMT</pubDate>
    <description>A dedicated [Build artifact retention policy](/en/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.</description>
  </item>
  <item>
    <title>Xcode compilation cache: new flag to disable caching without disabling analytics</title>
    <link>https://docs.bitrise.io/en/bitrise-ci/changelog#2026-03-10-xcode-compilation-cache-new-flag-to-disable-caching-without-disabling-analytics</link>
    <guid isPermaLink="false">https://docs.bitrise.io/en/bitrise-ci/changelog#2026-03-10-xcode-compilation-cache-new-flag-to-disable-caching-without-disabling-analytics</guid>
    <pubDate>Tue, 10 Mar 2026 00:00:00 GMT</pubDate>
    <description>The [Xcode compilation cache FAQ](/en/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.</description>
  </item>
  <item>
    <title>Build Cache: clear cache button replaces Settings dropdown</title>
    <link>https://docs.bitrise.io/en/bitrise-ci/changelog#2026-02-20-build-cache-clear-cache-button-replaces-settings-dropdown</link>
    <guid isPermaLink="false">https://docs.bitrise.io/en/bitrise-ci/changelog#2026-02-20-build-cache-clear-cache-button-replaces-settings-dropdown</guid>
    <pubDate>Fri, 20 Feb 2026 00:00:00 GMT</pubDate>
    <description>The [Clearing the Build Cache](/en/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.</description>
  </item>
  <item>
    <title>New guide: Endpoint Detection and Response (EDR) on Bitrise</title>
    <link>https://docs.bitrise.io/en/bitrise-ci/changelog#2026-02-20-new-guide-endpoint-detection-and-response-edr-on-bitrise</link>
    <guid isPermaLink="false">https://docs.bitrise.io/en/bitrise-ci/changelog#2026-02-20-new-guide-endpoint-detection-and-response-edr-on-bitrise</guid>
    <pubDate>Fri, 20 Feb 2026 00:00:00 GMT</pubDate>
    <description>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.</description>
  </item>
  <item>
    <title>OIDC for AWS guide updated</title>
    <link>https://docs.bitrise.io/en/bitrise-ci/changelog#2026-02-13-oidc-for-aws-guide-updated</link>
    <guid isPermaLink="false">https://docs.bitrise.io/en/bitrise-ci/changelog#2026-02-13-oidc-for-aws-guide-updated</guid>
    <pubDate>Fri, 13 Feb 2026 00:00:00 GMT</pubDate>
    <description>The [OIDC for AWS](/en/bitrise-platform/integrations/oidc-authentication/oidc-for-aws) guide has been updated with additional clarifications on configuration and usage.</description>
  </item>
  <item>
    <title>New guide: GitHub App migration API</title>
    <link>https://docs.bitrise.io/en/bitrise-ci/changelog#2026-02-03-new-guide-github-app-migration-api</link>
    <guid isPermaLink="false">https://docs.bitrise.io/en/bitrise-ci/changelog#2026-02-03-new-guide-github-app-migration-api</guid>
    <pubDate>Tue, 03 Feb 2026 00:00:00 GMT</pubDate>
    <description>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](/en/bitrise-ci/api/adding-and-managing-apps) for details.</description>
  </item>
  <item>
    <title>Tool setup: new tool versions added</title>
    <link>https://docs.bitrise.io/en/bitrise-ci/changelog#2026-01-27-tool-setup-new-tool-versions-added</link>
    <guid isPermaLink="false">https://docs.bitrise.io/en/bitrise-ci/changelog#2026-01-27-tool-setup-new-tool-versions-added</guid>
    <pubDate>Tue, 27 Jan 2026 00:00:00 GMT</pubDate>
    <description>The [Configuring tool versions](/en/bitrise-ci/configure-builds/configuring-build-settings/configuring-tool-versions) guide has been updated with newly supported tool versions in the tool setup feature.</description>
  </item>
  <item>
    <title>Build artifact retention policy documented</title>
    <link>https://docs.bitrise.io/en/bitrise-ci/changelog#2026-01-19-build-artifact-retention-policy-documented</link>
    <guid isPermaLink="false">https://docs.bitrise.io/en/bitrise-ci/changelog#2026-01-19-build-artifact-retention-policy-documented</guid>
    <pubDate>Mon, 19 Jan 2026 00:00:00 GMT</pubDate>
    <description>The [Build artifacts](/en/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.</description>
  </item>
  <item>
    <title>Pipeline rebuild: dynamic parallel workflows explained</title>
    <link>https://docs.bitrise.io/en/bitrise-ci/changelog#2026-01-12-pipeline-rebuild-dynamic-parallel-workflows-explained</link>
    <guid isPermaLink="false">https://docs.bitrise.io/en/bitrise-ci/changelog#2026-01-12-pipeline-rebuild-dynamic-parallel-workflows-explained</guid>
    <pubDate>Mon, 12 Jan 2026 00:00:00 GMT</pubDate>
    <description>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](/en/bitrise-ci/run-and-analyze-builds/build-data-and-troubleshooting/rebuilding-a-failed-build#rebuilding-a-failed-pipeline) for details.</description>
  </item>
  </channel>
</rss>