123 lines
6.1 KiB
YAML
123 lines
6.1 KiB
YAML
name: Gitea Version Tracker
|
|
|
|
on:
|
|
schedule:
|
|
# Daily at 08:00 UTC — check for new Gitea releases
|
|
- cron: '0 8 * * *'
|
|
workflow_dispatch:
|
|
inputs:
|
|
version:
|
|
description: 'Gitea version (e.g. 1.27.0) — leave empty to auto-detect'
|
|
required: false
|
|
|
|
jobs:
|
|
track:
|
|
name: Track Gitea Release
|
|
runs-on: ubuntu-latest
|
|
permissions:
|
|
contents: write
|
|
pull-requests: write
|
|
steps:
|
|
- uses: actions/checkout@v4
|
|
|
|
- name: Determine latest Gitea version
|
|
id: version
|
|
run: |
|
|
if [ -n "${{ github.event.inputs.version }}" ]; then
|
|
NEW_VERSION="${{ github.event.inputs.version }}"
|
|
else
|
|
# Fetch latest release from GitHub API (go-gitea/gitea mirror)
|
|
RELEASE_JSON=$(curl -sSf https://api.github.com/repos/go-gitea/gitea/releases/latest)
|
|
NEW_VERSION=$(echo "$RELEASE_JSON" | jq -r '.tag_name')
|
|
fi
|
|
# Strip 'v' prefix if present (API returns v1.27.0, we use 1.27.0)
|
|
NEW_VERSION="${NEW_VERSION#v}"
|
|
echo "New Gitea version: $NEW_VERSION"
|
|
|
|
# Parse marker line AND embedded OFFSET to locate the data row
|
|
MARKER_INFO=$(grep -n 'TRACKER:QUICK-REF-MAX' COMPATIBILITY.md)
|
|
MARKER_LINE=$(echo "$MARKER_INFO" | cut -d: -f1)
|
|
OFFSET=$(echo "$MARKER_INFO" | sed 's/.*OFFSET=\([0-9]*\).*/\1/')
|
|
CURRENT=$(sed -n "$((MARKER_LINE + OFFSET))p" COMPATIBILITY.md | awk -F'|' '{gsub(/\*| /, "", $4); print $4}')
|
|
echo "Current max tested: $CURRENT"
|
|
|
|
echo "new_version=$NEW_VERSION" >> $GITHUB_OUTPUT
|
|
echo "current_version=$CURRENT" >> $GITHUB_OUTPUT
|
|
|
|
if [ "$NEW_VERSION" = "$CURRENT" ]; then
|
|
echo "No new Gitea release detected. Skipping."
|
|
echo "skip=true" >> $GITHUB_OUTPUT
|
|
else
|
|
echo "New version detected: $CURRENT → $NEW_VERSION"
|
|
echo "skip=false" >> $GITHUB_OUTPUT
|
|
fi
|
|
|
|
- name: COMPATIBILITY.md — Quick Reference (max tested version)
|
|
if: steps.version.outputs.skip != 'true'
|
|
run: |
|
|
NEW="${{ steps.version.outputs.new_version }}"
|
|
# Parse marker line and embedded OFFSET to locate the data row
|
|
MARKER_INFO=$(grep -n 'TRACKER:QUICK-REF-MAX' COMPATIBILITY.md)
|
|
MARKER=$(echo "$MARKER_INFO" | cut -d: -f1)
|
|
OFFSET=$(echo "$MARKER_INFO" | sed 's/.*OFFSET=\([0-9]*\).*/\1/')
|
|
TARGET=$((MARKER + OFFSET))
|
|
# Update column 4 (Max Tested) and column 5 (Status) in the pipe-separated row
|
|
awk -i inplace -F'|' -v OFS='|' -v ver="${NEW}" '
|
|
NR == '$TARGET' { $4 = " **" ver "** "; $5 = " ⏳ Pending Verification " }
|
|
{ print }
|
|
' COMPATIBILITY.md
|
|
|
|
- name: COMPATIBILITY.md — Version History table
|
|
if: steps.version.outputs.skip != 'true'
|
|
run: |
|
|
NEW="${{ steps.version.outputs.new_version }}"
|
|
TODAY=$(date +%Y-%m-%d)
|
|
# Parse marker line and embedded OFFSET for the insertion point
|
|
MARKER_INFO=$(grep -n 'TRACKER:VERSION-INSERT' COMPATIBILITY.md)
|
|
MARKER=$(echo "$MARKER_INFO" | cut -d: -f1)
|
|
OFFSET=$(echo "$MARKER_INFO" | sed 's/.*OFFSET=\([0-9]*\).*/\1/')
|
|
INSERT=$((MARKER + OFFSET))
|
|
ROW="| **${NEW}** | ${TODAY} | ⏳ Pending Verification | TBD |"
|
|
sed -i "${INSERT}a ${ROW}" COMPATIBILITY.md
|
|
|
|
- name: README.md — pending badge
|
|
if: steps.version.outputs.skip != 'true'
|
|
run: |
|
|
NEW="${{ steps.version.outputs.new_version }}"
|
|
# Badge: update version, change label tested→pending, color blue→yellow
|
|
sed -i "/TRACKER:BADGE/s/%20[0-9a-z.-]*%20tested-blue/%20${NEW}%20pending-yellow/" README.md
|
|
|
|
- name: Create Pull Request
|
|
if: steps.version.outputs.skip != 'true'
|
|
uses: peter-evans/create-pull-request@v7
|
|
with:
|
|
branch: track/gitea-${{ steps.version.outputs.new_version }}
|
|
commit-message: "docs: track Gitea ${{ steps.version.outputs.new_version }} — pending verification"
|
|
title: "Track Gitea ${{ steps.version.outputs.new_version }} — ⏳ Pending Verification"
|
|
body: |
|
|
Gitea **${{ steps.version.outputs.new_version }}** has been released.
|
|
|
|
This PR:
|
|
- Updates the compatibility matrix in `COMPATIBILITY.md`
|
|
- Marks the new version as pending in the `README.md` badge
|
|
- Marks the new version as **⏳ Pending Verification**
|
|
|
|
## Verification Checklist
|
|
- [ ] Check [Gitea changelog](https://github.com/go-gitea/gitea/blob/main/CHANGELOG.md) for mail template changes
|
|
- [ ] Review diff of official templates: `git diff v${{ steps.version.outputs.current_version }}..v${{ steps.version.outputs.new_version }} -- templates/mail/ services/mailer/`
|
|
- [ ] Run `cd tools && go run . preview all` to confirm templates still render
|
|
- [ ] Run `cd tools && go test ./...` to verify push-notification data paths
|
|
- [ ] Update status from ⏳ to ✅ (compatible) or ❌ (breaking) in COMPATIBILITY.md
|
|
- [ ] Update the `Mail Template Changes` and `Breaking?` columns with accurate notes
|
|
- [ ] After verification, update `TRACKER:LATEST-VERIFIED` and the English/Chinese `TRACKER:LATEST-TESTED` lines; switch the README badge from pending to tested
|
|
|
|
## Semantic tracking
|
|
Once verified, update the tracked Gitea version:
|
|
- [ ] If templates changed, mark the top **Template Release** row `Unreleased` until the fix is tagged; if no change is needed, retain the verified release tag
|
|
- [ ] Update the README release status and compatibility matrix to distinguish source fixes from published packages
|
|
- [ ] Write `.github/release-notes/vX.Y.Z.md` before tagging; the release workflow uses this file for the published notes
|
|
- [ ] Tag a new release when shipping template fixes — `git tag vX.Y.Z && git push origin vX.Y.Z` (the release workflow packages automatically)
|
|
labels: compatibility, automated
|
|
env:
|
|
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
|