docs: clarify Gitea 1.27.3 fix is on main, not yet released
This commit is contained in:
1 parent
dfb5024dfb
commit
4ff008e564
4 files changed
+13
-13
No files matched your search
@@ -67,7 +67,7 @@ docs/ # Bilingual documentation (English + Simplified Chinese)
|
||||
## Versioning
|
||||
|
||||
- Release tags identify actual downloadable packages; the compatibility matrix distinguishes released tags from source-only fixes
|
||||
- The current published release is **v1.27.2**; it has a push-notification bug in Bloom, Ember, and Heritage on Gitea 1.27.1+. The current source tree fixes it and is verified against Gitea 1.27.3. The quick-reference table in `COMPATIBILITY.md` lists the unreleased row first; the tracker workflow updates that row by position
|
||||
- The current published release is **v1.27.2**; it has a push-notification bug in Bloom, Ember, and Heritage on Gitea 1.27.1+. The fix is on `main` and verified against Gitea 1.27.3. The quick-reference table in `COMPATIBILITY.md` lists the `main (unreleased)` row first; the tracker workflow updates that row by position
|
||||
- When a new Gitea version is checked: update the top `COMPATIBILITY.md` row and README badge; keep unreleased fixes distinct from the published release, and update verified/tested wording only after verification
|
||||
- Tag a new release (`vX.Y.Z`) only when the template content itself changes — the release workflow packages automatically on tag push
|
||||
- Keep the `TRACKER:` markers in `COMPATIBILITY.md` / `README.md` adjacent to their rows so the automated workflow keeps parsing them
|
||||
|
||||
Reference in new issue
Block a user