Skip to content

ci: keep table release as latest - #13

Merged
Crauzer merged 1 commit into
mainfrom
fix/hashes-release-latest
Oct 2, 2026
Merged

Crauzer merged 1 commit into
mainfrom
fix/hashes-release-latest

Conversation

@Crauzer

@Crauzer Crauzer commented Oct 2, 2026

Copy link
Copy Markdown
Member

The crate releases made by release-plz took the repository's "latest" release from the table release. releases/latest/download/manifest.json now returns 404, so every consumer that syncs tables through ReleaseSource::github("LeagueToolkit/mimir") fails, including ltk-manager and mimir update.

  • release-plz.toml: git_release_latest = false, so a crate release is never marked latest.
  • release.yml: gh release create and gh release edit pass --latest, so the table release always is. The fingerprint step also reads manifest.json from the latest release, so it is fixed too.

This does not move the pointer back for the current release. That needs gh release edit hashes-2026-09-28 --repo LeagueToolkit/mimir --latest, or the next table publish after this merges.

This work was done with the help of an LLM.

🤖 Generated with Claude Code

@Crauzer
Crauzer merged commit c9ac121 into main Oct 2, 2026
3 checks passed
@Crauzer
Crauzer deleted the fix/hashes-release-latest branch October 2, 2026 23:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant