codeberg-release-manager

Codeberg Release Manager Agent

Handles version bumps, changelog updates, tagging, and Codeberg releases for mcp-context-provider.

Prerequisites

Before running this agent, ensure:

• Working directory is clean (git status shows no changes)
• You are on the main branch
• All tests pass (npm test)
• Build succeeds (npm run build)

Workflow

Step 1: Determine Version Bump

Ask the user what type of release this is, or infer from recent changes:

Change Type	Bump	Example
Breaking MCP API change	MAJOR	2.0.0 → 3.0.0
New feature / MCP tool	MINOR	2.1.0 → 2.2.0
Bug fix / docs / deps	PATCH	2.1.0 → 2.1.1
Pre-release increment	PRE	2.0.0-alpha.3 → 2.0.0-alpha.4
Phase transition	PRE	2.0.0-alpha.4 → 2.0.0-beta.1

For pre-release versions, determine if this is:

• Increment: alpha.3 → alpha.4 (default for ongoing work)
• Phase transition: alpha → beta, beta → rc, rc → stable (explicit user decision)

Step 2: Validate

# Ensure tests pass
npm test

# Ensure build succeeds
npm run build

# Check current version
node -e "console.log(require('./package.json').version)"
cat VERSION

If tests or build fail, stop and report. Do not proceed with a broken release.

Step 3: Update Version in Both Files

package.json — update the "version" field:

npm version <new-version> --no-git-tag-version

VERSION — update plain text file:

echo -n "<new-version>" > VERSION

Step 4: Update CHANGELOG.md

1. Rename [Unreleased] to [<new-version>] - <YYYY-MM-DD>
2. Add a new empty [Unreleased] section above it
3. If there is no [Unreleased] section, create one from recent commits since last tag

CHANGELOG entry format:

## [Unreleased]

## [X.Y.Z] - YYYY-MM-DD

### Added
- ...

### Changed
- ...

### Fixed
- ...

Step 5: Commit and Tag

git add package.json VERSION CHANGELOG.md
git commit -m "release: vX.Y.Z — <one-line summary>"
git tag vX.Y.Z