Skip to content

fix: use semver-based latest detection for releases#6

Merged
dvcdsys merged 1 commit intomainfrom
claude/fix-release-tagging-9jBUo
Mar 23, 2026
Merged

fix: use semver-based latest detection for releases#6
dvcdsys merged 1 commit intomainfrom
claude/fix-release-tagging-9jBUo

Conversation

@dvcdsys
Copy link
Copy Markdown
Owner

@dvcdsys dvcdsys commented Mar 23, 2026

Set make_latest: "legacy" so GitHub determines the latest release
based on semantic versioning rather than marking every new release
as latest regardless of version order.

https://claude.ai/code/session_01QBX4wtsg4wwyhcyZhG7GpS


Note

Low Risk
Low risk workflow change limited to GitHub Release metadata; the main impact is which tag gets marked as the repository’s “latest” release.

Overview
Updates the release-cli.yml GitHub Actions workflow to set make_latest: "legacy" on the softprops/action-gh-release step so GitHub determines the “latest” release using semantic version ordering instead of always marking the newly created release as latest.

Written by Cursor Bugbot for commit b2be20a. This will update automatically on new commits. Configure here.

Set make_latest: "legacy" so GitHub determines the latest release
based on semantic versioning rather than marking every new release
as latest regardless of version order.

https://claude.ai/code/session_01QBX4wtsg4wwyhcyZhG7GpS
@dvcdsys dvcdsys merged commit 6d40a70 into main Mar 23, 2026
5 checks passed
@dvcdsys dvcdsys deleted the claude/fix-release-tagging-9jBUo branch March 23, 2026 05:54
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.

2 participants