lhumina_code/hero_skills
24
0
Fork 0
Code Issues 1 Pull requests Projects Releases 1 Packages 1 Wiki Activity Actions

Clean release strategy: versioned-only, drop latest tag #40

New issue
Closed
opened 2026-03-04 15:20:21 +00:00 by mik-tf · 0 comments
mik-tf commented 2026-03-04 15:20:21 +00:00
Owner
Copy link

Problem

The current release setup uses a latest tag/release that never updates its created_at timestamp, causing confusion on the releases page. There are also duplicate assets and an empty v1.0.0 release.

Solution

  • Remove latest release concept entirely
  • Only publish on v* tags (versioned releases)
  • install.sh uses Forgejo /releases/latest API endpoint (returns newest non-draft release automatically)
  • Development branch pushes run build + test only (no publish)
  • Delete stale latest and empty v1.0.0 releases
  • Start fresh with clean v1.0.0 release
## Problem The current release setup uses a `latest` tag/release that never updates its `created_at` timestamp, causing confusion on the releases page. There are also duplicate assets and an empty `v1.0.0` release. ## Solution - Remove `latest` release concept entirely - Only publish on `v*` tags (versioned releases) - `install.sh` uses Forgejo `/releases/latest` API endpoint (returns newest non-draft release automatically) - Development branch pushes run build + test only (no publish) - Delete stale `latest` and empty `v1.0.0` releases - Start fresh with clean `v1.0.0` release
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
development
main
latest
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
lhumina_code/hero_skills#40
No description provided.