Repos were transferred from the deivid user to a dedicated torrentclaw organisation; the workflows reference the org path.
68 lines
2 KiB
YAML
68 lines
2 KiB
YAML
name: Release
|
|
|
|
on:
|
|
push:
|
|
tags:
|
|
- "v*"
|
|
workflow_dispatch:
|
|
|
|
permissions:
|
|
contents: write
|
|
|
|
jobs:
|
|
release:
|
|
runs-on: docker
|
|
container:
|
|
image: docker.io/library/node:22
|
|
steps:
|
|
- uses: actions/checkout@v4
|
|
with:
|
|
fetch-depth: 0
|
|
|
|
- name: Install dependencies
|
|
run: npm ci
|
|
|
|
- name: Build
|
|
run: npm run build
|
|
|
|
- name: Test
|
|
run: npm test
|
|
|
|
- name: Publish to npm
|
|
env:
|
|
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
|
|
run: |
|
|
# Set authToken explicitly — actions/setup-node was the only consumer
|
|
# of registry-url + NODE_AUTH_TOKEN, and we dropped it for Forgejo
|
|
# compat. The literal npmjs registry stays the same.
|
|
cat > ~/.npmrc <<EOF
|
|
registry=https://registry.npmjs.org/
|
|
//registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN}
|
|
EOF
|
|
npm publish
|
|
rm -f ~/.npmrc
|
|
|
|
- name: Create Forgejo release with auto-generated notes
|
|
env:
|
|
FORGEJO_TOKEN: ${{ secrets.GITHUB_TOKEN }}
|
|
FORGEJO_API: http://forgejo:3000/api/v1
|
|
REPO: torrentclaw/torrentclaw-mcp
|
|
TAG: ${{ github.ref_name }}
|
|
run: |
|
|
set -euo pipefail
|
|
apt-get update && apt-get install -y --no-install-recommends jq curl
|
|
|
|
# Compose release body from commits since the previous tag.
|
|
prev=$(git describe --tags --abbrev=0 "${TAG}^" 2>/dev/null || echo "")
|
|
if [ -n "$prev" ]; then
|
|
notes=$(git log --pretty=format:'- %s' "${prev}..${TAG}")
|
|
else
|
|
notes=$(git log --pretty=format:'- %s' "${TAG}")
|
|
fi
|
|
body=$(jq -n --arg t "$TAG" --arg n "$notes" \
|
|
'{tag_name:$t, name:$t, body:$n, draft:false, prerelease:false}')
|
|
curl -sSf -X POST "$FORGEJO_API/repos/$REPO/releases" \
|
|
-H "Authorization: token $FORGEJO_TOKEN" \
|
|
-H "Content-Type: application/json" \
|
|
-d "$body" >/dev/null || \
|
|
echo "Release may already exist for $TAG"
|