enola 0.5.1 → 0.5.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 35717854ffb165b2d79fe06be0998d847a25a0ce10a2907ab155a39fd3119a75
-  data.tar.gz: 8940517eabb47871b5321fd23ed4f369cc7f31486f2f486096fdf78cd8e6cbcc
+  metadata.gz: 0f5c39f1dcc7577ecde43a125b51c74b640ec8f10ce6d38e4008bec02d7e8df6
+  data.tar.gz: 3a56415c6823950a6e115dbbe1b282f564e609211ee65609ef39b7e5daa35f15
 SHA512:
-  metadata.gz: cd181d1618ba05ebea4a77136ed6fc5d3afd197978c955576e1c8554d374b7558c3b4b0bd12b87e14f4c88642ff55faa6a5e8ef35bf12e33963fe7345418a778
-  data.tar.gz: 89206de715d8b08d9b7138cf4400df93b9385cf8b45c94bb08aa7de7b90f01267398e4d5da1f1ed3a4e87cd58ad33cf1e5f7492a6480ccee647a9129806ec142
+  metadata.gz: 9f2727a63a05b9aee2c24023014d7363c1b2fac11e4ad4cea85473d14bb4534fe769d5ff6e6c3ee6b71fd2a853cadd0d2dc67b72772d5188c2a63b7e05a5c033
+  data.tar.gz: 98734b4d06a0867d8808f023e59276d6c1b8e9dec27703078c5ae98f8dd02a2bd2add19606f42d4442f914b21818839af4bb5717448af5180aafd5ebb88453ca

data/CHANGELOG.md

@@ -1,3 +1,18 @@
+## enola 0.5.2, enola-rb 0.5.2, munola 0.5.2 and munola-rb 0.5.2 (2026-08-23)
+
+Rubydex is off in the config these gems write, and named in a comment beside
+the reason. The release each gem drives carries a walk that can fail to
+return: a constant reference spanning lines could be treated as its own
+predecessor, so a tree with vendored gems could snapshot for twenty-six
+minutes and several gigabytes without finishing. Two of the three Rails trees
+it was tried on did exactly that.
+
+The fix exists and is not yet in a published enola, so the default cannot
+depend on it. Prism is unaffected and stays on: it parses a monolith in 13.7
+seconds. Uncommenting the two lines brings Rubydex back for anyone who wants
+it deliberately, and the default returns the moment the binary each gem drives
+carries the fix.
+
 ## enola 0.5.1 (2026-08-23)
 
 The resolver no longer probes its own binstub. It read a candidate's first 512

data/lib/enola/config.rb

@@ -20,9 +20,11 @@ module Enola
 
     def self.render(ruby: Providers.ruby)
       <<~YAML
-        # Written by the enola gem; edit freely. Both providers are on by default:
-        # Prism runs under the Ruby that runs the gem, Rubydex is built into the
-        # binary and fetched once. Remove one to leave it out of the graph.
+        # Written by the enola gem; edit freely. Prism is on by default and runs
+        # under the Ruby that runs the gem. Rubydex is left off: the release this
+        # gem drives has a walk that can fail to return on a tree with vendored
+        # gems, fixed but not yet in a published enola. Uncomment it to run it
+        # anyway, and expect a snapshot that may not finish.
         repo: .
         repos:
           - .
@@ -32,8 +34,8 @@ module Enola
           - name: prism
             command: [#{ruby.inspect}, #{Providers.prism_script.inspect}]
             expected_version: "#{Providers.prism_version || '0.1.0'}"
-          - name: rubydex
-            expected_version: "#{Providers::RUBYDEX_EXPECTED_VERSION}"
+        # - name: rubydex
+        #   expected_version: "#{Providers::RUBYDEX_EXPECTED_VERSION}"
       YAML
     end
   end

data/lib/enola/version.rb

@@ -4,5 +4,5 @@ module Enola
   # The gem versions itself. UPSTREAM_VERSION names the enola release it
   # fetches and drives.
   UPSTREAM_VERSION = "0.4.4"
-  VERSION = "0.5.1"
+  VERSION = "0.5.2"
 end

metadata

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