2026.09.77 — 2026-09-30

Added

• Report a bug and review a support bundle in the UI (cf3168b9)

  Every signed-in user can now choose "Report a bug…" in the user menu. It opens a form pre-filled with Studio's version, Java, OS, database, sign-in providers, installed plugins and the browser. "Copy as Markdown" works without internet; "Open on GitHub" opens a new issue only when clicked, and nothing is sent until it is submitted there.

  Administration → Diagnostics prepares a support bundle, shows every section exactly as it will be written with each redacted value highlighted and counted, lets the administrator search a section and leave sections out, and downloads the zip. A prepared bundle expires after ten minutes; the screen counts down and offers to prepare it again.

• Support bundle and bug-report summary API (9ce8fd17)

  Administrators can prepare a support bundle and download it as a zip: about (versions, Java, OS, database, clusters), settings, health with details, the feature and plugin list, a thread dump and the most recent log lines. Every section is redacted by the credential rules, and no section reads a message. The download is written from the previewed snapshot, holds only the sections kept, and is recorded in the audit log as CREATE_DIAGNOSTICS_BUNDLE. A snapshot expires after ten minutes and only the administrator who prepared it can use it.

  The new permission diagnostics:bundle guards it; the built-in Admin role holds it already. Any signed-in user can read GET /api/v1/diagnostics/summary, the environment a bug report needs.

  Studio now keeps its last 5 000 log lines in memory, redacted, so the bundle has logs even though Studio logs to stdout only.

Fixed

• Keep the report dialog open once the user menu closes (2e3fc219)

  The dialog lived inside the menu's dropdown and closed with it. The user-menu slot now contributes a title and a dialog; the menu lists the title and hosts the dialog outside itself. The environment block wraps long values, and the title placeholder no longer reads like an entered title.

• Keep the dev and demo brokers healthy on apache/artemis 2.57.0 (c346228e)

  The apache/artemis 2.57.0 image ships without curl or wget, so every broker healthcheck failed, the brokers stayed unhealthy and the backups, which wait for a healthy primary, never started. The healthchecks now query Jolokia with bash alone, and the demo and end-to-end scripts reach each broker's Jolokia through its published port instead of running curl inside the container.