This directory holds a source winget manifest for HunterBown.CodeWhale (resolves #1561).
Not what winget serves today. The package published in microsoft/winget-pkgs (checked 2026-10-04, latest 0.10.0) is a different, multi-file manifest:
InstallerType: portable, one x64 installer (codewhale-tui-windows-x64.exe),Commands: codewhale, and a VC++ 2015+ x64 runtime dependency. It has no ARM64 installer and nocodewalias. The singleton below (NSIS + ZIP, x64/arm64,codewhale+codew) is stale at 0.9.6 and has never been what winget installs. Before the next submission, base it on the published manifest or update both together, and keep the identifierHunterBown.CodeWhale(this file usedHmbown.CodeWhaleuntil 2026-10-04, which would have created a second package).
The singleton was written so winget installs the single runtime under
codewhale + codew and never a codewhale-tui command. GitHub Releases
retain byte-identical codewhale-tui-* filenames only for legacy updater
compatibility.
HunterBown.CodeWhale.yaml— singleton manifest forwinget install HunterBown.CodeWhale. The installers all point at the signed (or checksum-verified) GitHub Release assets for the same version (CodeWhaleSetup.exefor x64 NSIS, plus portable ZIP fallbacks for x64/arm64).generate-winget-manifest.sh— bumpsPackageVersion,ReleaseDate, and the fourInstallerSha256placeholders from a localrelease-assets/checkout..winget/HunterBown.CodeWhale.yaml(repo root) is a verbatim mirror for tooling that expects.winget/. Keep both in sync;packaging/winget/HunterBown.CodeWhale.yamlis canonical.
- Tag
vX.Y.ZpublishesCodeWhaleSetup.exe,codewhale-windows-x64.zip,codewhale-windows-x64-portable.zip,codewhale-windows-arm64.zip,codewhale-windows-arm64-portable.zip, andcodewhale-artifacts-sha256.txt. - From the release tag checkout, run:
It rewrites both
./packaging/winget/generate-winget-manifest.sh X.Y.Z /path/to/release-assets
packaging/winget/HunterBown.CodeWhale.yamland.winget/HunterBown.CodeWhale.yamlwith the fresh version and the four SHA-256 values extracted fromcodewhale-artifacts-sha256.txt. - Validate locally with
winget validate(requires winget + the manifest schema):winget validate --manifest packaging/winget/HunterBown.CodeWhale.yaml # or the Microsoft validator in winget-pkgs CI: # https://github.com/microsoft/winget-pkgs#validation
- Submit to microsoft/winget-pkgs via
wingetcreateor a manual PR that addsmanifests/h/HunterBown/CodeWhale/X.Y.Z/:The generated PR must pass the winget-pkgs validation workflow before merge.wingetcreate update HunterBown.CodeWhale --version X.Y.Z --urls \ https://github.com/codewhale-hq/CodeWhale/releases/download/vX.Y.Z/CodeWhaleSetup.exe \ https://github.com/codewhale-hq/CodeWhale/releases/download/vX.Y.Z/codewhale-windows-x64.zip \ https://github.com/codewhale-hq/CodeWhale/releases/download/vX.Y.Z/codewhale-windows-x64-portable.zip \ https://github.com/codewhale-hq/CodeWhale/releases/download/vX.Y.Z/codewhale-windows-arm64.zip \ https://github.com/codewhale-hq/CodeWhale/releases/download/vX.Y.Z/codewhale-windows-arm64-portable.zip
Until v0.9.4 the release matrix installed three commands (codewhale, codew,
and codewhale-tui). Since v0.9.5 each target installs only the byte-identical
codewhale + codew commands (Windows also ships codewhale.bat). GitHub
Releases retain codewhale-tui-* compatibility filenames for old updater
clients, but the winget ZIP NestedInstallerFiles lists only the two current
PATH commands; codewhale-tui.exe is intentionally absent.
FreeBSD has no prebuilt GitHub Release asset (see docs/INSTALL.md § FreeBSD). Install via Cargo:
pkg install -y rust pkgconf # or ports-mgmt/pkg
cargo install codewhale-cli --locked # provides `codewhale`The npm wrapper on FreeBSD exits with Unsupported platform: freebsd and points to the Cargo path.
A native pkg install codewhale port is tracked as a follow-up to #1097 — contributions welcome
under packaging/freebsd/.