keelapps Releases for Bitbucket

Releases for Bitbucket

For the tag that says nothing about what shipped

A tag should say what shipped, and who approved it.

GitHub has had release pages since 2013. In Bitbucket Cloud a tag is still a name on a commit. Releases for Bitbucket turns every tag into a release: its notes from git, the pull requests it brought with who approved them, whether it built, and its files in Downloads. Export any release as Markdown or JSON. Nothing to configure, and nothing leaves Bitbucket.

Install free

Free on every workspace. Bitbucket Cloud apps are not billed through the Marketplace.

Read-only. Two read scopes, no storage, and the app declares no external network access.

Works in
Bitbucket Cloud
Runs on
Atlassian Forge
Your data
Never sent to us
Price
Free
A release opened from the Releases page: v1.2.0, tagged at ac0fc84, with the Evidence tab showing three things to check (a pull request merged by its own author with no other approval, and two commits that went in without a pull request) and three that passed: the build, coverage and tests.
The Evidence tab on a release. What someone should look at comes first; what passed follows, read from Bitbucket the moment you open it.

The gap this fills

BCLOUD-11404 — attach release notes and artifacts to tags, like GitHub Releases — has been open since 2015. Bitbucket Cloud lists tags, and stops there: no notes, no list of what changed, no files.

So a release lives in a wiki page someone writes by hand, a changelog nobody links, and a Slack thread. When an auditor asks who approved what went out in 2.3.0, someone spends an afternoon in the commit log.

Capabilities

What it does

Every tag, as a release

A Releases page in the repository sidebar, newest first, with the latest final release and pre-releases marked, and a Latest release card on the Source page.

Notes from git, not from the app

The annotated tag's message, or the version's section of CHANGELOG.md at the tagged commit. Nobody can edit them in the app afterwards.

What changed since the last release

The pull requests in the release with their authors, approvers and Jira work item keys, and every commit that went in without one.

The evidence behind it

Which pull requests someone else approved, which were merged by their own author, whether the tagged commit built, and every Code Insights report on it.

Its files, from Downloads

The files in Downloads whose names carry the version, so a release shows its build output without anyone attaching it by hand.

Markdown and JSON export

Copy a release as Markdown for a wiki page, a customer or a change ticket, or as JSON for an audit file.

On the release

Every pull request since the last tag

The Changes tab of release v1.1.0: two pull requests with their author, approvers and Jira work item keys TAL-12 and TAL-15, then four commits that went in without a pull request.
The Changes tab. Pull requests with who wrote and who approved them, the Jira work items they name, and every commit that skipped review.

Walkthrough

From a tag to a release anyone can read

  1. Install the app on your workspace

    Install it as a workspace administrator. Every repository gets a Releases page and a Latest release card. There are no settings.

  2. Tag the way you already do

    git tag -a v1.4.0 -m "…", or a section for 1.4.0 in CHANGELOG.md. Tags you pushed years ago are releases too.

  3. Open Releases in the sidebar

    Each release has its notes, its pull requests and approvals, its build and reports, and its files.

  4. Export it

    Paste the Markdown into Confluence or a change ticket, or file the JSON with your audit evidence.

Compared honestly

Against what Bitbucket does today

Question Bitbucket Cloud Releases for Bitbucket
Release notes on a tag? No — the tag message only in git From the tag or the changelog, on a release page
What changed since the last release? Compare two refs by hand Pull requests and direct commits, per release
Who approved what shipped? Open each pull request Approvers per pull request, self-merges flagged
Files attached to a release? No — Downloads is one flat list Matched to the release by version

Limits

Limits we state up front

It shows what git and Bitbucket recorded. Notes you never wrote are not invented: a tag with no message and no changelog section shows its pull request titles and says so.

Tags, not a release workflow. It does not create tags, draft notes or upload files. Your pipeline and your git habits stay as they are.

Big releases are cut short. A release reads up to 500 commits and 60 pull requests, and the newest 1,000 tags are listed. Past that, the page says so.

Availability

Free, on every Bitbucket Cloud workspace.

A workspace administrator installs Releases for Bitbucket from Atlassian's install page in one click. There is no paid tier: Bitbucket Cloud apps are not billed through the Marketplace.