The winget manifest for BonsaiFoundation.Bonsai is still at 2.9.0.0, so winget install BonsaiFoundation.Bonsai serves the previous release. The 2.9.1 installer shipped on 2026-07-06 and needs a matching 2.9.1.0 manifest published to microsoft/winget-pkgs. This is the manual version of what #2046 proposes automating, so it doubles as a concrete case for it.
The update is a one-liner with wingetcreate, which downloads the asset, computes InstallerSha256, bumps PackageVersion across the three manifests, and opens the winget-pkgs pull request:
wingetcreate update BonsaiFoundation.Bonsai --version 2.9.1.0 --urls https://github.com/bonsai-rx/bonsai/releases/download/2.9.1/Bonsai-2.9.1.exe --submit
Only the version, installer URL, InstallerSha256, and ReleaseDate change. Confirm the release asset is named Bonsai-2.9.1.exe before submitting.
The change itself is a pull request to microsoft/winget-pkgs, not this repository; this issue only tracks it as a sub-task of #2046.
The winget manifest for
BonsaiFoundation.Bonsaiis still at2.9.0.0, sowinget install BonsaiFoundation.Bonsaiserves the previous release. The 2.9.1 installer shipped on 2026-07-06 and needs a matching2.9.1.0manifest published to microsoft/winget-pkgs. This is the manual version of what #2046 proposes automating, so it doubles as a concrete case for it.The update is a one-liner with
wingetcreate, which downloads the asset, computesInstallerSha256, bumpsPackageVersionacross the three manifests, and opens the winget-pkgs pull request:Only the version, installer URL,
InstallerSha256, andReleaseDatechange. Confirm the release asset is namedBonsai-2.9.1.exebefore submitting.The change itself is a pull request to microsoft/winget-pkgs, not this repository; this issue only tracks it as a sub-task of #2046.