Hi Bitbucket Community!
Bitbucket Pipelines now gives you more control over what each step can access. You can let pipelines from chosen branches push to restricted branches, and use a short-lived OAuth token in your build instead of long-lived credentials.
Why we're making these changes
Automating releases often meant storing long-lived credentials in repository variables, or loosening branch protections so a pipeline could push. These changes let each step get only the access it needs, while your restricted branches stay protected.
What's new
- Benefit: A pipeline on
release can push a version bump to main, while pipelines on other branches cannot.
- Configure auth.system.scopes to control the permissions of the short-lived BITBUCKET_OAUTH_TOKEN. The token is limited to the repository running the pipeline and expires when the step finishes. When cloning is enabled, read:git:bitbucket is added automatically.
What's changing
Date | Change |
|---|
Oct 28, 2026 (already live) | The Run a pipeline API now requires write access. OAuth consumers, Connect apps, and access tokens need the pipeline:write scope in addition to pipeline |
Nov 30, 2026 | Pipelines can no longer push to restricted branches by adding the workspace user to the branch restriction. |
Apr 30, 2027 | Steps without auth.system.scopes get no scopes by default, or only read:git:bitbucket if clone is enabled. |
What you need to do
- Now: If you trigger pipelines through the API with an OAuth consumer, Connect app, or access token, make sure it has both the
pipeline and pipeline:write scopes. - Before 30 November 2026: configure Pipelines write access if relying on the workspace-user branch exemption.
- Before 30 April 2027: declare additional permissions needed by steps using built-in authentication.
- If you use self-hosted runners, upgrade them to version 6.1.0 or later.
Learn more
Share your feedback
We'd love to hear how this works for your team. Please share your feedback, questions, or bugs in this thread.