yamine 0.9.0 → 0.9.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 65dc796c2e121f6376d6a76b1baa7bb1ada3598c7facf8634262c83915c9cf2c
-  data.tar.gz: 0a2cea7a624133d68512b79e5e1060a96337a7da4948504313ea24ba6ecce080
+  metadata.gz: 10912afade2197809c63bc0d6382d754eaa236f5996462a242554775f9e48c1e
+  data.tar.gz: f2100f695bc378b3bf95ad2089907e614eea6deea10cc4f3029a98397439eea0
 SHA512:
-  metadata.gz: c1f73c73193f3e9c4eae8615ad0b790111bd2c6f29615a19f35c380e99db2d2a1a239e38b10c9328795a6f1c7cf1b28b0ecce721cb5414710769ba63a99b622b
-  data.tar.gz: 2200ab3b518fac757902b25e7ec2e6933d08e2183830aba2bbf5d893622b2ded021cc7bf4f07064e6efe9ff7500dad408ea73f7bc30a4c83c25b645829bdfdf2
+  metadata.gz: abfaa410dd665fb70e0d280b0ba0142607a095fc94ea3c88c5ea213cf32dec415fd0fec6723770a3a346a2b5ce4042d0b23a78d7796bb50e280f11fad7dedb13
+  data.tar.gz: ffef03352feb6c30328769b6e6e5c87705458b711cb0b5cc7a7c0b0b6b9061c06ece931766cbd4c2ec9cf09e397f2fdacaf2ee6fcb87c6e707e9163026457926

data/CHANGELOG.md

@@ -1,5 +1,32 @@
 # 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
+
+- **`proxy stop` no longer says "not running" while a root service is
+  serving.** With nothing recorded — the shape left by a service
+  installed by a gem version that did not record state — it returned
+  `:not_running` even though 443 answered, sending people to hunt for a
+  process that was right there. It now detects the serving proxy and
+  points at `sudo yamine service uninstall`.
+
+
 ## [0.9.0] — 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/proxy_control.rb

@@ -285,6 +285,12 @@ module Yamine
       pid = read_pid(store)
       port = proxy_port(store)
       if pid.nil?
+        # Nothing recorded, but a service can still be serving — a
+        # root-installed proxy from an older gem recorded no state at all,
+        # and "Proxy is not running." while 443 answers would be a lie
+        # that sends people looking for a process that is right there.
+        return :needs_root if serving_port(store)
+
         return :not_running unless port && listening?(port)
 
         return :unknown_process

data/lib/yamine/version.rb

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

metadata

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