Templates were re-checked against the local gitea clone (v1.27.1 tag): all
46 translation keys exist in locale_en-US, all data paths match the official
templates, and all 110 templates render via `go run . preview all` — no
template changes required.
From now on release versions mirror the Gitea version they support:
- COMPATIBILITY.md: quick reference now leads with release 1.27.1
(max tested Gitea 1.27.1, active), v1.0.x marked superseded; new
Versioning section documents the scheme
- README: release version in header + versioning bullet
- Tracker workflow PR body: added semantic-versioning release checklist
(bump Template Release column, tag vX.Y.Z)
Co-Authored-By: Claude <noreply@anthropic.com>
Gitea 1.27.1 fixed the mail template for push events (#38467) —
commit data must now be accessed via .UserCommit.GitCommit instead
of directly on the commit object.
Changed across all 10 themes:
- {{.ID}} → {{.UserCommit.GitCommit.ID}}
- {{.ID.String}} → {{.UserCommit.GitCommit.ID.String}}
- {{.MessageTitle}} → {{.UserCommit.GitCommit.MessageTitle}}
Verification:
- 3 mail-related files changed in Gitea v1.27.0→v1.27.1
- All 110 templates (10 themes × 11 types) render successfully
- No breaking changes — data structure unchanged, only access path
Co-Authored-By: Claude <noreply@anthropic.com>
Verification results:
- 0 files changed in templates/mail/ or services/mailer/ between v1.26.0 and v1.27.0
- All 110 templates (10 themes × 11 types) render successfully
- No new mail template types, no removed types
- No changes to template functions or data contexts
- No breaking changes for mail templates
Marking v1.0.1 as compatible with Gitea 1.27.0.
Co-Authored-By: Claude <noreply@anthropic.com>
v1.0.1 is a patch release with:
- Floating collapsible preview panel
- Ink theme mobile layout fixes
- Responsive topbar with multi-row wrapping
- CSS overflow prevention for mobile viewports
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>
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>
KenanZhuandClaude
KenanZhu