Script 'mail_helper' called by obssrc
Hello community,

here is the log from the commit of package openai-codex for openSUSE:Factory 
checked in at 2026-10-10 15:37:41
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/openai-codex (Old)
 and      /work/SRC/openSUSE:Factory/.openai-codex.new.3698736 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "openai-codex"

Sat Oct 10 15:37:41 2026 rev:19 rq:1383988 version:0.162.1

Changes:
--------
--- /work/SRC/openSUSE:Factory/openai-codex/openai-codex.changes        
2026-10-09 21:47:35.413886422 +0200
+++ /work/SRC/openSUSE:Factory/.openai-codex.new.3698736/openai-codex.changes   
2026-10-10 15:37:42.984942312 +0200
@@ -1,0 +2,12 @@
+Sat Oct 10 10:49:19 UTC 2026 - Martin Pluskal <[email protected]>
+
+- Update to version 0.162.1:
+  * Fixed a TUI crash on multiline asynchronous questions,
+    preserving line breaks and complete hyperlink destinations
+  * Fixed startup failures from a running background server whose
+    feature settings differ from the CLI defaults; compatibility
+    checks now apply only to explicit command-line overrides
+  * No Cargo.lock change, so the vendored tree carries over
+    unchanged and the License tag is untouched
+
+-------------------------------------------------------------------

Old:
----
  codex-rust-v0.162.0.tar.gz

New:
----
  codex-rust-v0.162.1.tar.gz

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

Other differences:
------------------
++++++ openai-codex.spec ++++++
--- /var/tmp/diff_new_pack.yKALDt/_old  2026-10-10 15:37:44.410001757 +0200
+++ /var/tmp/diff_new_pack.yKALDt/_new  2026-10-10 15:37:44.411001799 +0200
@@ -17,7 +17,7 @@
 
 
 Name:           openai-codex
-Version:        0.162.0
+Version:        0.162.1
 Release:        0
 Summary:        OpenAI Codex coding agent for the terminal
 # Legal-Review-Notice: upstream codex is Apache-2.0. Everything after that
@@ -55,6 +55,9 @@
 # with the same scope the set is unchanged, so the tag above is unchanged
 # by that bump. codex-cloud-client is new in the lock but is not linked
 # into codex-cli.
+# 0.162.1 moves no crate at all - Cargo.lock is byte-identical to 0.162.0's
+# and the only source delta is first-party codex code (Apache-2.0) - so the
+# tag above is unchanged by that bump.
 #  - self_cell 1.2.2 is "Apache-2.0 OR GPL-2.0-only" and is the ONLY crate
 #    anywhere in the graph offering GPL. Apache-2.0 is elected, so this
 #    package carries no GPL obligation; please do not re-derive it as GPL.

++++++ _service ++++++
--- /var/tmp/diff_new_pack.yKALDt/_old  2026-10-10 15:37:44.465004052 +0200
+++ /var/tmp/diff_new_pack.yKALDt/_new  2026-10-10 15:37:44.469004219 +0200
@@ -11,11 +11,11 @@
     feature and leaves the lockfile, hence the vendored set, untouched.
     To regenerate:
 
-      tar xf codex-rust-v0.162.0.tar.gz
-      patch -p1 -d codex-rust-v0.162.0 < codex-drop-v8-code-mode.patch
-      rm -rf codex-rust-v0.162.0/codex-rs/vendor
+      tar xf codex-rust-v0.162.1.tar.gz
+      patch -p1 -d codex-rust-v0.162.1 < codex-drop-v8-code-mode.patch
+      rm -rf codex-rust-v0.162.1/codex-rs/vendor
       osc service manualrun cargo_vendor
-      rm -rf codex-rust-v0.162.0
+      rm -rf codex-rust-v0.162.1
 
     The codex-rs/vendor removal drops the bundled bubblewrap 0.11.2 C sources,
     which %prep removes as well - codex uses the system bubblewrap instead.
@@ -60,7 +60,7 @@
     bump, not anything this package can vendor around.
   -->
   <service name="cargo_vendor" mode="manual">
-    <param name="srcdir">codex-rust-v0.162.0/codex-rs</param>
+    <param name="srcdir">codex-rust-v0.162.1/codex-rs</param>
     <param name="compression">zst</param>
     <param name="update">false</param>
   </service>

++++++ codex-rust-v0.162.0.tar.gz -> codex-rust-v0.162.1.tar.gz ++++++
/work/SRC/openSUSE:Factory/openai-codex/codex-rust-v0.162.0.tar.gz 
/work/SRC/openSUSE:Factory/.openai-codex.new.3698736/codex-rust-v0.162.1.tar.gz 
differ: char 13, line 1

Reply via email to