Beachball

Free plan

What Beachball is

Beachball automates semantic version updates, changelog generation, and npm publishing for JavaScript packages. It supports both single-package repositories and monorepos, with a default setup that does not require extra configuration to get started. The workflow uses `beachball change` to create change files, `beachball check` to validate them in pull requests, and `beachball publish` to release. Change files record a change type and description for reviewers. Publishing generates changelog files unless that step is disabled, can send packages to public or private npm registries, and can push version and changelog updates to the Git remote. CI guidance covers GitHub Actions and Azure Pipelines, alongside general advice for other CI platforms. An included helper can create and revoke repository-scoped GitHub App installation tokens; it requires Node 22.18 or later. Beachball is MIT-licensed and can be installed with npm or Yarn, or run using npx. The guidance recommends restricting token permissions and limiting release secrets to release builds or branches. If publishing fails after some versions reach the registry, the documented recovery is to run `beachball sync` and commit the changes.

Who it suits

Beachball suits JavaScript package maintainers who want versioning, changelog, and npm publishing workflows for single packages or monorepos. It also fits teams using GitHub Actions or Azure Pipelines.

What it does well

Supports monorepos and single-package repositories.
Creates change files for pull-request review.
Publishes to public or private npm registries.
Free and MIT licensed.

What to know first

Auth helper requires Node 22.18 or later.
Azure DevOps lacks npm trusted publishing support.
Partial publish failures require sync and a commit.

Plans

Plan	Billed and limits	Price
Beachball	MIT licensed · install as a devDependency or run via npx	Free

As microsoft.github.io lists them, read 4 Oct 2026. The maker's own page has the final word.

Getting started

Install Beachball as a development dependency with npm or Yarn, or run it with npx.
Create a change file with `beachball change`.
Run `beachball check` to validate change files in pull requests.
Configure a CI workflow using the guidance for GitHub Actions, Azure Pipelines, or another CI platform.
Run `beachball publish` to release packages. If a release partly fails after versions reach the registry, run `beachball sync` and commit the changes.

Verdict

Beachball provides a defined path from change files to npm releases, with version checks and changelog updates. Teams using Azure DevOps need token-based authentication, and its auth helper has a specific Node requirement.

Questions

How much does Beachball cost?

The Beachball plan is free. It is MIT licensed.

Can I use Beachball for free?

Yes. Beachball is free and open source under the MIT license.

Which package managers can I use to install it?

The installation guide shows npm and Yarn. Beachball can also be run with npx.

Which registries can it publish to?

Beachball can publish packages to public or private npm registries.

Does it support CI platforms?

Its CI documentation covers GitHub Actions and Azure Pipelines, with general guidance for other platforms. Azure DevOps is not supported for npm trusted publishing, so token-based authentication is needed in that case.

What does the authentication helper require?

The helper can create and revoke repository-scoped GitHub App installation tokens. It requires Node 22.18 or later.

Facts from Beachball's own pages

AI support: Beachball provides a change-file skill that can be installed for compatible AI agents, including GitHub Copilot and Claude Code. · microsoft.github.io, 11 Oct 2026
Authentication: The CI guidance recommends limiting token permissions and restricting release secrets to release builds or branches. · microsoft.github.io, 11 Oct 2026
Authentication utility: The package includes an auth helper that can create and revoke repository scoped GitHub App installation tokens. · microsoft.github.io, 4 Oct 2026
Changelogs: Beachball generates changelogs when it bumps package versions. · microsoft.github.io, 11 Oct 2026
Change tracking: Change files record the change type and description for package updates, and reviewers can inspect them in the pull request diff. · microsoft.github.io, 4 Oct 2026
Configuration: Beachball can be used without extra configuration by default, and supports repository and package configuration. · microsoft.github.io, 11 Oct 2026
Founded: 2019 · microsoft.github.io, 28 Sept 2026
Installation: The installation guide shows npm and Yarn commands and says Beachball can also be run with npx. · microsoft.github.io, 4 Oct 2026
Integrations: The CI documentation describes using Beachball with GitHub Actions and Azure Pipelines. · microsoft.github.io, 11 Oct 2026
License: Beachball is MIT licensed. · microsoft.github.io, 11 Oct 2026
Maker: The official site identifies Microsoft as the copyright holder; it does not state headquarters or founding year on the pages reviewed. · microsoft.github.io, 11 Oct 2026
Notable limitation: The documentation says Azure DevOps is not supported for npm trusted publishing, so token-based authentication is needed in that case. · microsoft.github.io, 11 Oct 2026
Publishing: Beachball can publish packages to public or private npm registries and push version and changelog updates to the Git remote. · microsoft.github.io, 4 Oct 2026
Publishing limitation: If a publish fails after some package versions have reached the registry, the documentation says to run `beachball sync` and commit the changes. · microsoft.github.io, 4 Oct 2026
Purpose: Beachball automates semantic version bumps, changelog generation, and npm publishing for JavaScript packages. · microsoft.github.io, 11 Oct 2026
Registries: Beachball can publish packages to public or private npm registries. · microsoft.github.io, 11 Oct 2026
Repository support: Beachball works with single-package repositories and monorepos. · microsoft.github.io, 11 Oct 2026
Runtime requirement: The auth helper requires Node 22.18 or later. · microsoft.github.io, 4 Oct 2026
Security guidance: For token based authentication, the CI guidance recommends minimum necessary permissions and storing tokens as secrets available only to release builds. · microsoft.github.io, 4 Oct 2026
Validation: Beachball checks the Git repository and npm registry before publishing. · microsoft.github.io, 11 Oct 2026
Version syncing: Beachball keeps versions in the Git repository and npm registry in sync during publishing. · microsoft.github.io, 11 Oct 2026
Workflow: Developers create change files, pull request builds can check that they are included, and releases run through CI or manually. · microsoft.github.io, 11 Oct 2026

Where Beachball stands on Freedom251

Release automation tools#8 of 34
Monorepo Management Tools#18 of 33