mirror of
https://github.com/Ark0N/Codeman.git
synced 2026-11-14 10:39:32 +01:00
Codeman maintainer
e9b2ecd552
changesets/action copies a CHANGELOG.md section into the release as it stands, so a whole release rendered as one bullet behind its commit hash, with `### Thanks` as literal text and "Minor Changes" as the only real heading. The Release workflow now rebuilds the body from that section: Thanks first, then What's new with a heading per change, Fixes, Also in this release and a compare link, with "Behaviour change:" and "Breaking:" in bold. The release is titled `Codeman <x.y.z>`; the tag stays `codeman@<x.y.z>`, which is what the updater and the update toast read. This cannot be written into CHANGELOG.md instead: `### <Type> Changes` is hardcoded upstream, and a `## ` line would end the section for changesets/action and versionSection(). So the changelog keeps its format and the toast is unaffected. npm has already published when the step runs, so a formatter failure leaves the changesets text with a warning and the retag still happens. SECTION_LABELS is now shared with whats-new.mjs so the toast and the page agree on what counts as a headline. docs/releasing.md records the changeset shape. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
102 lines
3.6 KiB
YAML
102 lines
3.6 KiB
YAML
name: Release
|
|
|
|
on:
|
|
push:
|
|
branches:
|
|
- master
|
|
|
|
concurrency: ${{ github.workflow }}-${{ github.ref }}
|
|
|
|
jobs:
|
|
release:
|
|
name: Release
|
|
runs-on: ubuntu-latest
|
|
permissions:
|
|
contents: write
|
|
pull-requests: write
|
|
outputs:
|
|
published: ${{ steps.changesets.outputs.published }}
|
|
steps:
|
|
- name: Checkout repo
|
|
uses: actions/checkout@v6
|
|
|
|
- name: Setup Node.js
|
|
uses: actions/setup-node@v6
|
|
with:
|
|
node-version: 22
|
|
cache: npm
|
|
registry-url: https://registry.npmjs.org
|
|
|
|
- name: Install dependencies
|
|
run: npm ci
|
|
|
|
- name: Build
|
|
run: npm run build
|
|
|
|
- name: Create release PR or publish
|
|
id: changesets
|
|
uses: changesets/action@v1
|
|
with:
|
|
publish: npm run release
|
|
version: npm run version-packages
|
|
title: "chore: version packages"
|
|
commit: "chore: version packages"
|
|
env:
|
|
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
|
|
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
|
|
|
|
- name: Rename release tag to codeman
|
|
if: steps.changesets.outputs.published == 'true'
|
|
env:
|
|
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
|
|
run: |
|
|
VERSION=$(node -p "require('./package.json').version")
|
|
OLD_TAG="aicodeman@${VERSION}"
|
|
NEW_TAG="codeman@${VERSION}"
|
|
|
|
# Update the GitHub release BEFORE deleting the old tag.
|
|
# make_latest pins the "Latest" badge to the Codeman release. This repo
|
|
# publishes TWO packages (aicodeman + xterm-zerolag-input), changesets
|
|
# creates a GitHub release for each, and GitHub awards "Latest" to
|
|
# whichever was published LAST. That is a race: 1.9.2 kept the badge,
|
|
# 1.9.4 lost it to xterm-zerolag-input@0.1.7 by two seconds. All package
|
|
# releases already exist by the time this step runs, so setting it here
|
|
# is deterministic.
|
|
#
|
|
# The title and body are the page people land on from the update toast.
|
|
# changesets copied the body from CHANGELOG.md as one long bullet, so it is
|
|
# reshaped here (scripts/lib/release-notes.mjs). npm has already published by
|
|
# now, so a failure in that must not stop the retag below: without the body
|
|
# field the release keeps the text changesets wrote.
|
|
RELEASE_ID=$(gh release view "$OLD_TAG" --json databaseId -q .databaseId 2>/dev/null || true)
|
|
if [ -n "$RELEASE_ID" ]; then
|
|
NOTES_FILE="$RUNNER_TEMP/release-notes.md"
|
|
BODY_ARGS=()
|
|
if node scripts/generate-release-notes.mjs "$VERSION" > "$NOTES_FILE"; then
|
|
BODY_ARGS=(-F "body=@$NOTES_FILE")
|
|
else
|
|
echo "::warning::Keeping the changesets release notes for $VERSION"
|
|
fi
|
|
gh api -X PATCH "repos/${{ github.repository }}/releases/${RELEASE_ID}" \
|
|
-f tag_name="$NEW_TAG" \
|
|
-f name="Codeman ${VERSION}" \
|
|
-f make_latest=true \
|
|
"${BODY_ARGS[@]}"
|
|
fi
|
|
|
|
# Retag
|
|
git tag "$NEW_TAG" "$OLD_TAG" 2>/dev/null || true
|
|
git tag -d "$OLD_TAG" 2>/dev/null || true
|
|
git push origin "$NEW_TAG" ":refs/tags/$OLD_TAG" 2>/dev/null || true
|
|
|
|
# Its own job: this one alone holds id-token, and a registry failure shows as itself
|
|
# without touching the npm publish or the tag above.
|
|
mcp-registry:
|
|
name: MCP registry
|
|
needs: release
|
|
if: needs.release.outputs.published == 'true'
|
|
permissions:
|
|
contents: read
|
|
id-token: write
|
|
uses: ./.github/workflows/publish-mcp.yml
|