Script 'mail_helper' called by obssrc
Hello community,

here is the log from the commit of package bugwarden for openSUSE:Factory 
checked in at 2026-09-08 16:53:56
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/bugwarden (Old)
 and      /work/SRC/openSUSE:Factory/.bugwarden.new.1265 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "bugwarden"

Tue Sep  8 16:53:56 2026 rev:5 rq:1376024 version:0.6.0

Changes:
--------
--- /work/SRC/openSUSE:Factory/bugwarden/bugwarden.changes      2026-08-19 
18:01:47.960486655 +0200
+++ /work/SRC/openSUSE:Factory/.bugwarden.new.1265/bugwarden.changes    
2026-09-08 16:54:56.750050917 +0200
@@ -1,0 +2,30 @@
+Sun Sep  6 14:52:40 UTC 2026 - Martin Pluskal <[email protected]>
+
+- 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
+
+-------------------------------------------------------------------

Old:
----
  bugwarden-0.5.0.obscpio
  bugwarden-0.5.0.tar.zst

New:
----
  bugwarden-0.6.0.obscpio
  bugwarden-0.6.0.tar.zst

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ bugwarden.spec ++++++
--- /var/tmp/diff_new_pack.9cl2wX/_old  2026-09-08 16:54:57.904099333 +0200
+++ /var/tmp/diff_new_pack.9cl2wX/_new  2026-09-08 16:54:57.909099543 +0200
@@ -17,7 +17,7 @@
 
 
 Name:           bugwarden
-Version:        0.5.0
+Version:        0.6.0
 Release:        0
 Summary:        MCP server for Bugzilla with operator-controlled security 
guards
 # Upstream is Apache-2.0; the rest is the aggregate of the crates statically

++++++ _service ++++++
--- /var/tmp/diff_new_pack.9cl2wX/_old  2026-09-08 16:54:57.955101473 +0200
+++ /var/tmp/diff_new_pack.9cl2wX/_new  2026-09-08 16:54:57.959101640 +0200
@@ -2,7 +2,7 @@
   <service name="obs_scm" mode="manual">
     <param name="url">https://github.com/plusky/bugwarden.git</param>
     <param name="scm">git</param>
-    <param name="revision">0.5.0</param>
+    <param name="revision">0.6.0</param>
     <param name="versionformat">@PARENT_TAG@</param>
     <param name="exclude">.git</param>
   </service>
@@ -12,10 +12,17 @@
     <param name="compression">zst</param>
   </service>
   <service name="set_version" mode="manual"/>
+  <!-- Vendor upstream's own Cargo.lock. Updating past that lock pulls
+       rmcp 3.2.0, which the "3.1" requirement accepts but which no longer
+       negotiates the 2026-07-28 protocol revision this release serves:
+       three %check tests then fail on the fallback to 2025-11-25.
+       source_validator's "missing update=true" note is expected here;
+       cargo_audit still runs, and it is clean for this lock. Re-test
+       update=true on the next release rather than carrying this blind. -->
   <service name="cargo_vendor" mode="manual">
     <param name="srcdir">bugwarden</param>
     <param name="compression">zst</param>
-    <param name="update">true</param>
+    <param name="update">false</param>
   </service>
   <service name="cargo_audit" mode="manual">
     <param name="srcdir">bugwarden</param>

++++++ bugwarden-0.5.0.obscpio -> bugwarden-0.6.0.obscpio ++++++
++++ 25920 lines of diff (skipped)

++++++ bugwarden-0.5.0.tar.zst -> bugwarden-0.6.0.tar.zst ++++++
++++ 25920 lines of diff (skipped)

++++++ bugwarden.obsinfo ++++++
--- /var/tmp/diff_new_pack.9cl2wX/_old  2026-09-08 16:54:58.527125471 +0200
+++ /var/tmp/diff_new_pack.9cl2wX/_new  2026-09-08 16:54:58.530125597 +0200
@@ -1,5 +1,5 @@
 name: bugwarden
-version: 0.5.0
-mtime: 1787124631
-commit: 527e580433fd5328d9fd8166a7cf50d4fb0c8a2e
+version: 0.6.0
+mtime: 1788704241
+commit: 5fe772acaea99c3892d32143a3c8c23c25e104bb
 

++++++ vendor.tar.zst ++++++
/work/SRC/openSUSE:Factory/bugwarden/vendor.tar.zst 
/work/SRC/openSUSE:Factory/.bugwarden.new.1265/vendor.tar.zst differ: char 7, 
line 1

Reply via email to