yamine 0.9.1 → 0.9.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 5059de08c17cccfe2d24ce5217a2c3c70fb5cc004a6eb528856eedf9b5389409
-  data.tar.gz: 19da6abd533f3f80cbdfda8553427ed987e1ba18f83d24cf37934c906d03caef
+  metadata.gz: 10912afade2197809c63bc0d6382d754eaa236f5996462a242554775f9e48c1e
+  data.tar.gz: f2100f695bc378b3bf95ad2089907e614eea6deea10cc4f3029a98397439eea0
 SHA512:
-  metadata.gz: 8a31f0124a322242398ef9e416fe46a7dd6ab13aac2265fb6ebc00743da14b82ef20ef30af8f3f018627bf6534779e074173a4795936c392de6b1df41c654a6a
-  data.tar.gz: 922a0dd3ce552a6a76f931ae50385a5f98bf5d87b7fcee13e44367b209c193dad3be8a526e23585950251251a10e8cbc324375ba71d06291c2d12964441a48ac
+  metadata.gz: abfaa410dd665fb70e0d280b0ba0142607a095fc94ea3c88c5ea213cf32dec415fd0fec6723770a3a346a2b5ce4042d0b23a78d7796bb50e280f11fad7dedb13
+  data.tar.gz: ffef03352feb6c30328769b6e6e5c87705458b711cb0b5cc7a7c0b0b6b9061c06ece931766cbd4c2ec9cf09e397f2fdacaf2ee6fcb87c6e707e9163026457926

data/CHANGELOG.md

@@ -1,5 +1,20 @@
 # Changelog
 
+## [0.9.2] — 2026-09-10
+
+### Fixed
+
+- **doctor's version check was blind to its own motivating case.** A
+  serving proxy that recorded no version predates the marker (added in
+  0.9.0), which means it is definitely not the code you have installed —
+  but with `version == nil` the check stayed silent. So the exact service
+  it exists to catch, a root service left behind by an older gem, kept
+  serving old code with doctor reporting `[ok] proxy state: consistent`.
+  It now warns and points at `sudo yamine service install`. (A machine
+  with no proxy at all is still silent — no version and nothing serving
+  is not a problem.)
+
+
 ## [0.9.1] — 2026-09-10
 
 ### Fixed

data/lib/yamine/doctor.rb

@@ -124,6 +124,15 @@ module Yamine
       if version && version != Yamine::VERSION
         problems << "the running proxy is v#{version}, this CLI is v#{Yamine::VERSION}" \
           " — re-register it: sudo yamine service install"
+      elsif version.nil? && serving
+        # A serving proxy that recorded no version predates the marker
+        # (added in 0.9.0), so it is definitely not the code we ship with
+        # now. Without this the version check was blind to exactly the
+        # service it exists to catch — an old root service keeps serving
+        # old code until it is re-registered.
+        problems << "the running proxy does not report a version (installed before " \
+          "v0.9.0), this CLI is v#{Yamine::VERSION}" \
+          " — re-register it: sudo yamine service install"
       end
 
       if problems.empty?

data/lib/yamine/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Yamine
-  VERSION = "0.9.1"
+  VERSION = "0.9.2"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: yamine
 version: !ruby/object:Gem::Version
-  version: 0.9.1
+  version: 0.9.2
 platform: ruby
 authors:
 - Kaka Ruto