Repository navigation
ci: publish releases from the changelog - #31
Merged
Merged
Conversation
A release workflow (tag push or manual run) builds every download the README lists, takes the notes from that version's CHANGELOG entry, adds the SHA256 of each file and publishes the GitHub release. WinLens.exe is kept as an alias of the x64 build so old download links still work. Also completes the 1.3.0 changelog entry.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested by Marco · project thread
Summary
Before: each release was assembled by hand: build, upload
WinLens.exe, write the notes, compute the SHA256. Only the x64 exe was attached, while the README lists four downloads.After: pushing a
v*tag, or running the release workflow with a version, builds the x64 and arm64 exe and standalone zips. It writes the notes from that version'sCHANGELOG.mdentry, in the same layout as v1.2.0, with the SHA256 of each file, and publishes the release.WinLens.exeis still attached as a copy of the x64 build, so old download links keep working.The 1.3.0 changelog entry also gains the last two changes from the manual test, and the
[1.3.0]link.Type of change
Checklist
dotnet build -c Release(no warnings)Generated by Claude Code