| AArch64 | |
| ppc64le | |
| s390x | |
| x86-64 |
- Update to 0.6.0:
* Add caller-selected field projection to bug_info and an opt-in
group_by projection to bugs_quicksearch
* Window large responses: head/tail for bug_comments and
bug_history, a per-comment character cap, and text windowing
for download_attachment
* Serialize tool responses as compact JSON
* Serve the 2026-07-28 MCP lifecycle and version-gate the
SEP-2549 cache hints on tools/list to it
* Move the audit stream to schema version 2: suppressed_ids_count
and suppressed_other_count replace the single suppressed count,
work_context is reserved, response_bytes is recorded and the
upstream block is populated
* Take the audit session id from the session layer instead of the
client-supplied header
* Cap and escape every client-controlled string that reaches an
audit record, a tracing line or a log sink, and bound a stdio
frame the way the HTTP transport bounds a body
* Arm the shutdown signals before announcing readiness, and
answer a handler panic instead of leaving the call unanswered
- Vendor upstream's own Cargo.lock instead of updating past it
(cargo_vendor update=false): the update pulls rmcp 3.2.0, which
the "3.1" requirement accepts but which no longer negotiates the
2026-07-28 revision this release serves, so three tests fail on
the fallback to 2025-11-25
- Vendored chacha20 is now 0.10.2; 0.5.0 shipped the yanked 0.10.1
- Update to 0.5.0:
* Let the environment set allowed hosts and the auth header
* Require a bearer token on the HTTP transport
* Export audit records and diagnostics to an OTLP collector
* Handle SIGTERM so container stop is graceful
* Refuse unparsable allowed-hosts at startup
* Normalize tool schemas for Gemini/Vertex clients, and recurse
portable_schema into all draft-2020-12 positions
- Vendored h2 bumped to 0.4.16 for RUSTSEC-2026-0258 /
GHSA-q83h-524g-xf6h (h2 unbounded empty DATA frames lead to
denial of service)
- Raise the rust BuildRequires floor from 1.85 to 1.88 to match
the workspace rust-version
- Refresh License: drop CDLA-Permissive-2.0, the
LGPL-2.1-or-later option, the Zlib option and the
LLVM-exception option, none of which remain in the linked
crate set
- Ship the worked OpenTelemetry collector example as documentation
- Move the shell completions into bash-completion, zsh-completion and fish-completion subpackages, so a shell's completions are only pulled in where that shell is installed
- Update to 0.4.0:
* Add product and field discovery tools, and accept custom fields
when filing a bug
* Add --allowed-hosts to restrict the inbound host header
* Fail startup when the identity cannot be resolved, and resolve it
from a declared, verified login so it no longer depends on the
local account
* Identify this build to Bugzilla with a User-Agent, and introduce
it by name in the MCP handshake
* Stop imposing one instance's status workflow on every instance
* Stop reading a capped search page as the end of results
* Stop shipping the example policy rule that depended on whoami
* Reserve the rule names the guard decides under
* Stop under-reporting suppressed_count as a maximum
* Derive the HTTP body cap from the attachment ceiling
* Move the server to rmcp 3.1 and pin what the transport may serve
* Move the Bugzilla client to reqwest 0.13
- Install the man page and the bash, zsh and fish completions, which
upstream now generates from the CLI definition and ships prebuilt
- Update to 0.3.0:
* The server can hold the Bugzilla API key itself via
- -api-key-file (container secret, systemd LoadCredential), so
over HTTP clients no longer have to present the real key
* New policy matcher created_by_me matches the bug-caller
relationship, letting a policy treat the requesting account's
own reports differently from everyone else's
* Policy rules are scoped by operation, fixing a rule granting
only create silently deciding - and denying - read access to
existing bugs in its products
* update_bug_fields gained named parameters for summary, url,
whiteboard, version, target_milestone and add/remove lists for
keywords and see_also, all under the existing fields capability
* Audit records adopt the W3C trace context from a client-supplied
traceparent, and bugs_quicksearch records how many rows the
search-window scan examined and how many it withheld
* The example policy installed as /etc/bugwarden/policy.toml was
reworked to demonstrate the new matchers; installs that edited
theirs keep it (the file is config noreplace)
- Add ca-certificates-mozilla to BuildRequires: the HTTP transport
tests new in this release refuse to construct their client while
the system CA store is empty
- Update to 0.2.0:
* Added the create_bug and add_attachment tools, growing the guard
capability vocabulary from eleven to thirteen
* An existing policy file is not rewritten on upgrade, so wherever it
grants allow it starts permitting bug filing and attachment upload;
keep the previous behaviour with disabled_tools = ["create_bug",
"add_attachment"] under [global], or replace allow grants with
restrict rules naming the capabilities meant
* Added an optional append-only JSONL audit stream recording every
tool call together with the guard's verdict, written only when named
with --audit-config or BUGWARDEN_AUDIT_CONFIG
* bugs_quicksearch now paginates over the bugs a client may see, so a
policy-filtered page no longer returns short
* Denied bug ids are scrubbed from bug bodies, history and comments
* bug_info bodies are served on their own verdict
* The example policy denies security groups by name
- Install the worked audit-stream example as %config(noreplace)
/etc/bugwarden/audit.toml, on the same terms as the policy example
- Initial package (version 0.1.0):
* MCP server exposing Bugzilla to Model Context Protocol clients,
gated by an operator-controlled guard policy the client can
neither read nor change
* worked example policy installed as %config(noreplace)
/etc/bugwarden/policy.toml; the server only reads a policy named
explicitly with --policy or BUGWARDEN_POLICY