release: finalize and publish DnsSwitcher v1.5.0 - #18
Merged
Conversation
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
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.
Summary
Finalizes stable
v1.5.0after completed Windows validation.Included
CHANGELOGclosed for1.5.0on 2026-08-19;docs/versions/v1.5.0.mdand synchronized release/version indexes;AGENTS.mdand.project-rules/*removed from Git tracking while remaining ignored by.gitignore;release/v1.5.0retained;publish-v1.5.0.ymlworkflow.Publication behavior
After squash merge to
main, the one-shot workflow:SHA256SUMS.txtagainst both final binaries;v1.5.0as a draft release, uploads all three assets, then makes it stable only if all uploads succeed;The workflow refuses to replace an existing
v1.5.0release.Validation
The owner confirmed all planned Windows tests pass. The publish workflow repeats automated build/tests and packaging on the exact final commit before release creation.
Known limitation
The repository is private, so anonymous in-app GitHub Releases discovery remains unavailable. No embedded GitHub credential workaround is introduced.