yamine 0.9.0 → 0.9.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 65dc796c2e121f6376d6a76b1baa7bb1ada3598c7facf8634262c83915c9cf2c
4
- data.tar.gz: 0a2cea7a624133d68512b79e5e1060a96337a7da4948504313ea24ba6ecce080
3
+ metadata.gz: 5059de08c17cccfe2d24ce5217a2c3c70fb5cc004a6eb528856eedf9b5389409
4
+ data.tar.gz: 19da6abd533f3f80cbdfda8553427ed987e1ba18f83d24cf37934c906d03caef
5
5
  SHA512:
6
- metadata.gz: c1f73c73193f3e9c4eae8615ad0b790111bd2c6f29615a19f35c380e99db2d2a1a239e38b10c9328795a6f1c7cf1b28b0ecce721cb5414710769ba63a99b622b
7
- data.tar.gz: 2200ab3b518fac757902b25e7ec2e6933d08e2183830aba2bbf5d893622b2ded021cc7bf4f07064e6efe9ff7500dad408ea73f7bc30a4c83c25b645829bdfdf2
6
+ metadata.gz: 8a31f0124a322242398ef9e416fe46a7dd6ab13aac2265fb6ebc00743da14b82ef20ef30af8f3f018627bf6534779e074173a4795936c392de6b1df41c654a6a
7
+ data.tar.gz: 922a0dd3ce552a6a76f931ae50385a5f98bf5d87b7fcee13e44367b209c193dad3be8a526e23585950251251a10e8cbc324375ba71d06291c2d12964441a48ac
data/CHANGELOG.md CHANGED
@@ -1,5 +1,17 @@
1
1
  # Changelog
2
2
 
3
+ ## [0.9.1] — 2026-09-10
4
+
5
+ ### Fixed
6
+
7
+ - **`proxy stop` no longer says "not running" while a root service is
8
+ serving.** With nothing recorded — the shape left by a service
9
+ installed by a gem version that did not record state — it returned
10
+ `:not_running` even though 443 answered, sending people to hunt for a
11
+ process that was right there. It now detects the serving proxy and
12
+ points at `sudo yamine service uninstall`.
13
+
14
+
3
15
  ## [0.9.0] — 2026-09-10
4
16
 
5
17
  ### Fixed
@@ -285,6 +285,12 @@ module Yamine
285
285
  pid = read_pid(store)
286
286
  port = proxy_port(store)
287
287
  if pid.nil?
288
+ # Nothing recorded, but a service can still be serving — a
289
+ # root-installed proxy from an older gem recorded no state at all,
290
+ # and "Proxy is not running." while 443 answers would be a lie
291
+ # that sends people looking for a process that is right there.
292
+ return :needs_root if serving_port(store)
293
+
288
294
  return :not_running unless port && listening?(port)
289
295
 
290
296
  return :unknown_process
@@ -1,5 +1,5 @@
1
1
  # frozen_string_literal: true
2
2
 
3
3
  module Yamine
4
- VERSION = "0.9.0"
4
+ VERSION = "0.9.1"
5
5
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: yamine
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.9.0
4
+ version: 0.9.1
5
5
  platform: ruby
6
6
  authors:
7
7
  - Kaka Ruto