Shivansh Garg a5201dc427 feat(release): allow setting a release as the latest (#40214) ...

Gitea picks the latest release by commit date, while GitHub keeps an
explicit pointer, so repositories migrated from GitHub could show a
different latest release than their source. Fixes
https://github.com/go-gitea/gitea/issues/35273.

- Add a "Set as Latest Release" checkbox and GitHub's `make_latest` API
option. Without them, the newest stable release by commit date stays the
latest.
- Migrations from GitHub and Gitea carry over the source's latest
release.
- Migrated releases are dated by their commit like native ones, and
equally dated ones keep the source's order.

<img width="355" height="122" alt="Set as Latest Release checkbox"
src="https://github.com/user-attachments/assets/d35f5324-7ae0-4e9f-b73c-d3c90496fb00"
/>

---------

Co-authored-by: silverwind <me@silverwind.io>

2026-11-06 08:23:13 +00:00

..

fileicon

chore(deps): update dependencies (#40168)

2026-11-02 19:30:55 +00:00

gitignore

Fix various typos in codebase (#35480)

2025-09-13 10:34:43 -04:00

label

feat: Add sorting by exclusive labels (issue priority) (#33206)

2025-04-10 17:18:07 +00:00

license

chore: update license files with line wrapping (#39726)

2026-10-11 00:57:21 +08:00

locale

feat(release): allow setting a release as the latest (#40214)

2026-11-06 08:23:13 +00:00

readme

Bindata is optional and over-writable on restart (#354)

2016-12-22 19:12:23 +01:00