GITHUB_TOKEN needs explicit contents: write to create releases via
softprops/action-gh-release. Without it, the API returns 403.
Co-Authored-By: Claude <noreply@anthropic.com>
cp -r requires the target directory to exist. Changed to mkdir -p the
full archive path instead of just dist/.
Co-Authored-By: Claude <noreply@anthropic.com>
When tracker detects a new Gitea version, the shields.io badge now
updates from 'tested-blue' to '待测试-yellow' to indicate pending
verification status.
Co-Authored-By: Claude <noreply@anthropic.com>
Markers now self-document their position: 'OFFSET=N' means the target
row is N lines below the marker. Workflow extracts offset dynamically
via sed, no hardcoded values.
Format: <!-- TRACKER:<NAME> OFFSET=<N> -->
Co-Authored-By: Claude <noreply@anthropic.com>
HTML comments between table rows broke markdown rendering. Moved both
tracker markers above table headers, updated workflow to use offsets:
- QUICK-REF-MAX: data row at marker + 3
- VERSION-INSERT: insert at marker + 2
Co-Authored-By: Claude <noreply@anthropic.com>
The workflow read MARKER-1 (line above marker = separator line),
returning '-----------------' as the version. The data row is BELOW
the marker. Fixed both read and update steps to use MARKER+1.
Co-Authored-By: Claude <noreply@anthropic.com>
grep -oP (Perl regex) failed on Ubuntu runner, returning empty current
version. Replaced version parsing with awk -F'|' to extract from the
pipe-separated Quick Reference table by column index.
Also replaced the Quick Reference update sed with awk -i inplace for
column-based editing, avoiding fragile regex on formatted table cells.
Co-Authored-By: Claude <noreply@anthropic.com>
Bug fixes found during cross-validation:
1. VERSION-INSERT marker placed before table header → moved after separator
line so new rows insert between separator and first data row.
2. Badge sed pattern 'tested\)-[0-9a-z.]*\(blue\)' never matched because
URL has 'tested-blue' not 'tested)-...'. Fixed to match URL-encoded
format: '%20<version>%20tested-blue'.
3. Quick Reference sed depended on '| ✅' status literal. Changed to
'| [^|]*' to match any status text, always setting to ⏳ on update.
4. Gitea API returns 'v1.27.0' tag_name but docs use '1.27.0'. Added
'${NEW_VERSION#v}' to strip v prefix.
Co-Authored-By: Claude <noreply@anthropic.com>
Add TRACKER: HTML comment markers to COMPATIBILITY.md, README.md, and
all 5 translation READMEs. Rewrite gitea-tracker.yml to use grep -n
for precise line-based insertion and sed line-address editing.
Markers introduced:
- TRACKER:QUICK-REF-MAX — Quick Reference max tested version
- TRACKER:VERSION-INSERT — Version History row insertion point
- TRACKER:LATEST-VERIFIED — latest verified note version
- TRACKER:BADGE — shields.io badge version
- TRACKER:LATEST-TESTED — latest tested version in READMEs
Co-Authored-By: Claude <noreply@anthropic.com>
- Create COMPATIBILITY.md with version matrix, Gitea release tracking,
template variable reference, and compatibility verification process
- Add Gitea 1.25+ | 1.26.4 tested badge to README
- Update all 6 READMEs (EN + 5 translations) with latest tested version
and link to COMPATIBILITY.md
- Include COMPATIBILITY.md in release artifacts
Co-Authored-By: Claude <noreply@anthropic.com>
- Validate all templates on push to main and tag v*
- On tag: package themes/ as zip + tar.gz and create GitHub release
Co-Authored-By: Claude <noreply@anthropic.com>
KenanZhuandClaude