github buggregator/server v2.11.1

38 minutes ago

Built with harnsy — the Buggregator team runs its AI agents in harnsy.

A security fix for the update from the UI added in v2.11.0. Update if you run v2.11.0.

Security

  • Only the Buggregator UI itself can start an update. In v2.11.0, with the default settings (no sign-in, open CORS), another web page open in the same browser could ask your local Buggregator to install the latest release — for example a dev server on another port of localhost, or any page in a browser that does not send Sec-Fetch-Site. It could only install the latest official signed release, but with the default in-memory database that restart loses your events. Now /api/update and /api/update/check accept requests only from the same origin as the UI, get no CORS headers, and are refused over the WebSocket API. (#454)

Changed

  • The install scripts check the release signature. install.sh and install.ps1 verify checksums.txt.sig with OpenSSL 3 before they install. A missing signature stops the install for v2.11.0 and later (BUGGREGATOR_NO_SIGNATURE=1 only for a mirror you trust). Without OpenSSL 3 they fall back to the SHA-256 check. How to check a download by hand: Verify a download. (#452)
  • Kubernetes update hint: two commands, --reset-then-reuse-values for Helm 3.14+ and --reuse-values for older Helm. (#453)

Upgrade

Click Update to 2.11.1 in Settings › About & updates, replace the binary, or pull the new image. There are no new database migrations. Bundled UI: frontend 1.38.0 (unchanged).

What's Changed

  • fix(selfupdate): Kubernetes update hint uses --reset-then-reuse-values by @butschster in #453
  • feat(install): verify checksums.txt.sig in install.sh / install.ps1 by @butschster in #452
  • fix(selfupdate): only the server's own page can start or check an update by @butschster in #454

Full Changelog: v2.11.0...v2.11.1

Don't miss a new server release

NewReleases is sending notifications on new releases.