enola-rb 0.5.0 → 0.5.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 29d16125df2191d08effd55d0fbac2499a593a86dc2fe4686ac3086caf8b8840
-  data.tar.gz: b40ed2edef51dc2c28c53c69192feb7a3c1cb9ac5088e004b320fa68bbf0fc92
+  metadata.gz: 9fbcd837c69e2e0a6b92dfbddc30d9aaac38f54213113b8d4d6a589320e32d27
+  data.tar.gz: 8792cc31cdda93b7babb26d0456d32df66b216c81f12d2ae65b9a7428f7f8006
 SHA512:
-  metadata.gz: 823742ff6c4312dad0bd245792958b641b6a4f0119b614df664bb860b97428deea65c458af875dc1fd02874ebab02b23e936a49fbf404a9ba4760a2e860670c7
-  data.tar.gz: 46fb4ff8b9f5b261a430e6b724831259471b633e5f7300bb2dbdebbaf45f13183695afb79965b99d2f01e1ae8b385da7a83049b78795111b3aa0e41a421bc4cd
+  metadata.gz: c74832d5048372be8512568349382cd78ec374dd05602ad2644cbc6657b7f40cadc1c83c202165ed907ef0bd49b43535672ea31c7420bedd961aee16c58b4593
+  data.tar.gz: 61c82759e4766c5de2ff211db8589e22d32f154a40c66137250bc323c854a07406d53c6ca40bd153c99ba5c8801b6cf1a9f0de1654e95531f0caef913b936bde

data/CHANGELOG.md

@@ -1,3 +1,23 @@
+## enola 0.5.1 (2026-08-23)
+
+The resolver no longer probes its own binstub. It read a candidate's first 512
+bytes looking for the marker RubyGems writes, and a real binstub carries a
+`/bin/sh` + `ruby -x` preamble holding the interpreter's absolute path, which puts
+that marker around byte 580 — outside the window. So the guard missed every
+RubyGems-generated binstub, the wrapper ran itself, and running itself has no
+bottom: `enola --version` on a cold cache spawned Ruby processes until it was
+killed. The whole file is read now, capped at 64 KiB so a released binary is never
+slurped only to be rejected, and `Gem.bin_path` is recognised beside
+`Gem.activate_bin_path`. A probe also marks its child's environment, and a resolver
+that sees the marker declines to look at PATH at all, so the recursion is bounded
+by construction rather than by how well a heuristic reads a file.
+
+The marker is written where it is spawned: every probe passes it into the child,
+so a wrapper reached under another name leaves PATH alone instead of probing in
+turn. That bound is what covers the wrappers the content check cannot see, a
+version manager's shim among them, which carries none of the markers a binstub
+does. Reported and fixed by dejo1307 in #1.
+
 ## munola 0.4.4.2 and munola-rb 0.4.4.2 (2026-08-23)
 
 munola follows the channel it drives. Its binary is now cut from the stable

data/lib/enola_rb/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module EnolaRb
-  VERSION = "0.5.0"
+  VERSION = "0.5.1"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: enola-rb
 version: !ruby/object:Gem::Version
-  version: 0.5.0
+  version: 0.5.1
 platform: ruby
 authors:
 - Muhamed Isabegovic