fix: windows installer on release tags - #368
Merged
Merged
Conversation
daniel-rdt
reviewed
Jan 13, 2026
daniel-rdt
left a comment
daniel-rdt
left a comment
Member
There was a problem hiding this comment.
Thanks @coroa. Looks good, but I do have a question regarding the state of the repo after running git branch --force master HEAD.
Co-authored-by: Daniel Rüdt <117752024+daniel-rdt@users.noreply.github.com>
daniel-rdt
approved these changes
Jan 13, 2026
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
2 participants
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.
Changes proposed in this Pull Request
Follow-up to #333 .
The release github action now makes sure the release installers come with the repository set up on the master branch pointing to the release tag, so that
will fetch and merge the latest master.
Checklist
A release notedoc/release_notes.rstis added.