munola 0.6.0 → 0.6.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 558cd383ea993d03a3a667a3287a7ae27db1f8a41642e63bce0727846a1af987
-  data.tar.gz: 5cd95dccec42025f8cea27b8b6aaa528f8a1f7e4b17ddb1be53541a12bf62268
+  metadata.gz: f9aaf4515e419373749156b376859f5385d8770bd6c3f6c4954f483008dd7594
+  data.tar.gz: 86f089c88a6fb0b843e91b10cc1c3e88d897198f8a9f1fa81764a265fce3733e
 SHA512:
-  metadata.gz: 2a47d2376487ef8e19cf22b5f66d00f32eb1ab8e7cab3750846ccc048a6739ec5cd7f6f4e7a527079a7c5ca3555baeb5d2ac7cf9000c2aa4ed772e225d30be0b
-  data.tar.gz: 51e549f4e966e6ad231f7618c2b9e7826a84fa0b2c8972c3fd35ff666128bfdf2d0f2b9fda657139b1548ac2ae9a2f76c138e75e8c178a9ebc95f9aa3a7c5ccb
+  metadata.gz: 640e95eea31e3cb19b93c1af6bd9351e8411ab7093d42713dba0f920cf4851c74ec144d64a08e01d5aa5b9863940b9a1d888708687dfb2c9cdfc37b20f4c0012
+  data.tar.gz: e09afd9a96fba881ae389297f43447b4a6909f4e297f688a91d78ccb63747457773debdbe477ace4a6beaf5d00622712b361af6ebccfe1a98bde8e8d88797f5a

data/CHANGELOG.md

@@ -1,3 +1,42 @@
+## munola 0.6.2 (2026-08-30)
+
+munola drives channel release `0.4.10.1`, cut from the promoted current at
+upstream enola 0.4.10. The difference list shrank again by contribution: the
+exclusion filter went upstream in 0.4.7, and the constraints reference this
+channel once carried inside INTENT.md shipped upstream as CONSTRAINTS.md and
+PROVIDERS.md over 0.4.5. What the channel still adds is the recipe catalogue
+at enola-guides v0.3.1, the init role binding, the cache-version double
+history and a readability spelling in blame.go.
+
+## enola 0.5.4 and enola-rb 0.5.4 (2026-08-30)
+
+The gems drive upstream enola 0.4.10. Between 0.4.6 and here upstream took the
+exclusion filter (#255, in 0.4.7), rescored the layers explainer per language
+cohort (0.4.7), began reading package manifests as dependency facts with a
+declared-purpose diff (0.4.8), gave the dashboard its own command (0.4.9), and
+documented the snapshot artifacts as a versioned contract with fact identity
+(0.4.10). The vendored Prism provider script and the Rubydex engine pin are
+byte-identical across the span, so nothing re-vendors; the wrappers move by
+the release they name.
+
+## munola 0.6.1 (2026-08-24)
+
+munola drives channel release `0.4.6.1`, cut from the promoted current at
+upstream enola 0.4.6. The prefix walk fix is in the binary this gem fetches,
+so the expiry the 0.6.0 note named is met and Rubydex is on by default again.
+The channel still carries the exclusion filter, which upstream merged an hour
+after 0.4.6 was published, so an excluded document is skipped before its
+definitions are read: 440 seconds to 193 on a Rails monolith, facts identical.
+
+The 0.6.0 note said munola waits on Prism alone. On the Rails install path it
+did not. `munola init` reuses enola-rb's installer, which writes
+`mcp-arch.yaml` first, and munola's own writer yields to a file that already
+exists, so the config every Rails project got was the enola gem's, with both
+providers on, against a channel binary built before the fix. Two things follow.
+The config and the binary now agree, which is what closes it. And munola's
+writer has a test that reads munola's writer, rather than one that reads the
+file enola-rb wrote and reports on munola.
+
 ## enola 0.5.3, enola-rb 0.5.3 and munola 0.6.0 (2026-08-24)
 
 Both providers are on again. enola-labs shipped the prefix walk fix in 0.4.6,

data/lib/munola/providers_config.rb

@@ -27,10 +27,7 @@ module Munola
       else
         lines << "  # prism: the enola gem on this machine carries no provider script; add one here to run it"
       end
-      lines += ["  # rubydex is off until the channel release carries the walk fix:",
-        "  # a reference spanning lines could be its own predecessor, so a tree with",
-        "  # vendored gems could snapshot without ever finishing. Uncomment to run it.",
-        "  # - name: rubydex", "  #   expected_version: \"#{RUBYDEX_VERSION}\""]
+      lines += ["  - name: rubydex", "    expected_version: \"#{RUBYDEX_VERSION}\""]
       "#{lines.join("\n")}\n"
     end
 

data/lib/munola/version.rb

@@ -3,7 +3,7 @@
 module Munola
   # UPSTREAM_VERSION names the enola release this channel is built on,
   # CHANNEL_VERSION the fork release the gem fetches.
-  UPSTREAM_VERSION = "0.4.4"
-  CHANNEL_VERSION = "0.4.4.2"
-  VERSION = "0.6.0"
+  UPSTREAM_VERSION = "0.4.10"
+  CHANNEL_VERSION = "0.4.10.1"
+  VERSION = "0.6.2"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: munola
 version: !ruby/object:Gem::Version
-  version: 0.6.0
+  version: 0.6.2
 platform: ruby
 authors:
 - Muhamed Isabegovic
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2026-08-24 00:00:00.000000000 Z
+date: 2026-08-30 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: enola
@@ -56,8 +56,8 @@ description: |
   The binary this gem fetches is not an enola-labs release. It is a build
   cut from https://github.com/misabegovic/enola, a fork of enola, whose
   release notes name what differs from upstream release by release; this
-  gem drives channel release 0.4.4.2, built on enola
-  0.4.4. Everything else is the enola gem's wrapper,
+  gem drives channel release 0.4.10.1, built on enola
+  0.4.10. Everything else is the enola gem's wrapper,
   unchanged: fetched on first use, verified against the checksums the
   release publishes, cached per user, every command and exit code
   forwarded. Use the enola gem to run stock upstream instead.