monorelReleases for Go monorepos

Explicit per-PR changesets. The tag conventions Go modules need.

Changeset files, not commit messages

Every release-affecting PR includes a .changeset/.md file naming affected packages and bump levels. No path-attribution leaks, no Release-As footers stripped by squash-merges.

Native Go tag conventions

Bare vX.Y.Z for the main module, /vX.Y.Z for sub-modules. The format go install actually expects, configurable per package.

Always-open release PR

The bot orchestrator force-pushes a speculative-version branch and upserts a PR. Reviewable, mergeable. The CLI also works standalone for local dry-runs.

Pre-release support

monorel pre enter rc switches the repo into release-candidate mode; pre exit returns to stable. Per-package counters; multi-channel.

Provider-neutral forge seam

GitHub today, GitLab / Gitea / Bitbucket / Forgejo by adding a subpackage. Renames, hosts, and auth shapes are encapsulated in the provider, not the orchestrator.

Self-hosted from day one

monorel releases itself with monorel. The same binary that ships your library cuts its own tags.

Quick Example

toml

# monorel.toml
[forge]
provider = "github"
owner    = "acme"
repo     = "widget"

[packages."github.com/acme/widget"]
tag_prefix = ""
path       = "."
changelog  = "CHANGELOG.md"

[packages."transports/zerolog"]
tag_prefix = "transports/zerolog"
path       = "transports/zerolog"
changelog  = "transports/zerolog/CHANGELOG.md"

# Author a changeset describing this PR
monorel add --package "transports/zerolog:minor" --message "Adds Lazy() helper."

# Preview the next release locally
monorel plan
# PACKAGE             FROM     BUMP   TO       TAG
# transports/zerolog  v1.6.1   minor  v1.7.0   transports/zerolog/v1.7.0
#
# 1 package(s) to release; 1 changeset(s) consumed.

# Apply: write CHANGELOGs, delete consumed changesets, commit, tag
monorel release
git push --follow-tags

That's the loop. The GitHub Action drives the same flow as an always-open release PR; merging the PR runs monorel release on the merge commit and publishes one GitHub Release per tag.