Bump version to 0.6.0 - #45
Merged
Merged
Conversation
The v0.6.0 tag fired release.yml, which checks the csproj <Version> against the tag and failed: the folder-sizes/navigation/triage work landed without touching the version, so the csproj still said 0.5.0. Bumps the two places that matter and the two that document them: csproj <Version>, build.ps1's -Version default, and the example commands in CLAUDE.md and README.md. Nothing shipped in a broken state. The v0.6.0 release exists with no assets, and CheckForUpdateAsync returns null when it finds no ExplorerHelper-Setup-*.exe among them, so installed copies read it as "no update" rather than offering a download that would 404. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
The
v0.6.0tag firedrelease.yml, which compares the csproj<Version>against the tag and failed:The folder-sizes / navigation / triage work in #44 landed without touching the version. That's my miss — CLAUDE.md says to bump both when cutting a release, and I didn't.
What changed
Four places, all tracking the newest tag:
src/ExplorerHelper/ExplorerHelper.csproj<Version>— the one CI actually checksbuild.ps1-Versiondefault — only affects local builds, since the workflow passes the tag explicitly, but it's the documented convention and a lagging default makes every local build think an update is waiting (issue [BUG] Local builds show a permanent "update available" pill: csproj Version lags the v0.5.0 tag #33)CLAUDE.mdandREADME.mdexample commandsNothing shipped broken
The
v0.6.0release exists, published and marked latest, with zero assets because the build never reached the upload step. That turns out to be harmless:CheckForUpdateAsyncscans the release's assets forExplorerHelper-Setup-*.exeand returns null when it finds none, so installed 0.5.0 copies read it as "no update" rather than showing a pill whose download would 404.Verified
./build.ps1 -Version 0.6.0publishes clean and producesExplorerHelper-0.6.0-win-x64.zip.ProductVersion: 0.6.0+7c048b9, soUpdateService.CurrentVersionwill match the tag and the binary won't report an update to itself.The installer step wasn't exercised locally (no Inno Setup here); CI covers it.
After merging
The tag still points at
7c048b9, which doesn't contain this bump, so it has to move before the release will build:That re-runs
release.yml, andsoftprops/action-gh-releaseupdates the existing release in place with the zip and installer attached.🤖 Generated with Claude Code