Skip to content

Release tooling fixes, changelog, and README updates for 0.1.5 - #57

Merged
kkaminsk merged 3 commits into
mainfrom
build/release-tooling-fixes
Oct 15, 2026
Merged

kkaminsk merged 3 commits into
mainfrom
build/release-tooling-fixes

Conversation

@kkaminsk

@kkaminsk kkaminsk commented Oct 15, 2026 •

Copy link
Copy Markdown
Owner

Release-tooling fixes found while shipping v0.1.5, plus a changelog and README updates for the release.

  • winget template no longer names a third-party brand. installer/winget/BigHatGroup.FileCommand.locale.en-US.yaml described FileCommand as recreating "the Norton Commander 5.5 workflow". winget-pkgs policy 1.2 flagged that wording on the 0.1.0 submission (New package: BigHatGroup.FileCommand version 0.1.0 microsoft/winget-pkgs#429006), and the approved replacement was only ever applied upstream. The template now carries the approved wording plus a comment explaining why, so a release built from the template matches what winget accepted. A manifest generated from it is identical to the 0.1.5 submission (New version: BigHatGroup.FileCommand version 0.1.5 microsoft/winget-pkgs#453550) and passes winget validate.
  • build.ps1 -Sign finds the signing tooling without overrides. The defaults pointed at C:\GitHub\CodeSigning, which does not exist on the current build machine, so v0.1.5 had to pass -CodeSigningDlib and -CodeSigningMetadata by hand. They now resolve from a CodeSigning checkout next to the repo root (C:\Temp\tsscat\CodeSigning beside C:\Temp\tsscat\FileCommand). Help text and installer/README.md are updated. Verified that the script still parses and both defaults resolve to existing files; the explicit overrides still work as before.
  • New CHANGELOG.md. Covers 0.1.0 through 0.1.5, taken from the published release notes, plus these unreleased fixes.
  • README brought up to date for 0.1.5. Links the changelog, shows winget install and choco install with their default scopes, and documents the conflict dialog's Cancel, quit-time job cleanup, partial-file copies, verified and link-safe moves, streaming listings, and how junctions and unreadable entries list.

The Chocolatey nuspec also mentions Norton Commander, but Chocolatey approved 0.1.2 and 0.1.4 with that text, so it is unchanged.

🤖 Generated with Claude Code

kkaminsk and others added 3 commits October 15, 2026 15:29
winget-pkgs policy 1.2 flagged the Norton Commander mention on the 0.1.0 submission (microsoft/winget-pkgs#429006). Use the wording that was approved there and shipped for 0.1.4 and 0.1.5, with a comment so it does not regress.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
build.ps1 -Sign defaulted to C:\GitHub\CodeSigning, which does not exist on the current build machine. Resolve the Trusted Signing dlib and metadata from a CodeSigning checkout next to the repo root instead (C:\Temp\tsscat\CodeSigning here), and update the help text and installer README.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
CHANGELOG.md covers every release from 0.1.0 to 0.1.5, taken from the published release notes, plus the unreleased release-tooling fixes. The README now links it, shows winget and Chocolatey install commands, and describes the conflict dialog's Cancel, partial-file copies, verified moves, link-safe moves, streaming listings, and junction listings.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@kkaminsk kkaminsk changed the title Release tooling: winget brand-free description, sibling CodeSigning default Release tooling fixes, changelog, and README updates for 0.1.5 Oct 15, 2026
@kkaminsk
kkaminsk merged commit 7410b74 into main Oct 15, 2026
2 of 3 checks passed
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.

1 participant