munola 0.6.1 → 0.6.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 035c3780ee982f7ae5ec0dc3613ae0d09d4e7ae6fc1a6c3bbe7d446da45548b5
-  data.tar.gz: 7f17a853e60b770fe08a90f9f055f1891f1c3f7d7a59c188ba44e8e0744a3d10
+  metadata.gz: 1e3d58d7520f207bf19748ef82fc4a57900ad2c306feff700b8bd87605b2a8fe
+  data.tar.gz: de640b108d6af206cb518670703811aaaba93eb16e995dd131c78a352e7d0a46
 SHA512:
-  metadata.gz: a50a5ba6d22316da864d6a1c15b5eee82a681e9e87d7de00590a211453ec7fa512cd6fae628ee94e800977f46a18e26201ffc5f4f98a8f7a537586e6fb7f96e7
-  data.tar.gz: 0c07b025c1f109e040f3af93de83be72e84b34de591956d95a1b91a25bd1daf7cbdaae9dbbc8fb49fc777d956dec5c0e64b010311e447dbafcf0cd20b8af325a
+  metadata.gz: cdb0f3a025d1a0b7cd9eed5fc6ed6eba9a53e085f1d1d0314cd60ecd4ed9188b91af162283473e617a1bd1c51879875ec36139d2ffa437e6dd768a6e80586cb2
+  data.tar.gz: 66f31031b985d9218a096b7549c0e0fe2be399cfad61d3a56c31fc30127974126dae7530510ce65f3da354f3e2c7e3ef39e2542a36c8fd79e54840fa17563eab

data/CHANGELOG.md

@@ -1,3 +1,58 @@
+## enola 0.5.5, enola-rb 0.5.5 and munola 0.6.3 (2026-09-14)
+
+The enola and enola-rb gems drive upstream enola 0.4.19. Between 0.4.10 and
+here upstream read GraphQL server schemas so client operations have something
+to match (0.4.12), bound Python imports to the module they name and added the
+import-closure explainer (0.4.13), resolved C++ calls when the short name is
+unique (0.4.13), published pip wheels and lowered the glibc floor to 2.17
+(0.4.14, 0.4.15), stopped constraint checks skipping struct owners and
+knowledge-page components (0.4.16), made the dashboard reload its snapshot on
+refresh and bound Python calls to symbols a package defines in its own
+`__init__.py` (0.4.17), made install.sh POSIX and gave upgrades their own
+checksum (0.4.18), and made the Stop hook report once per session (0.4.19).
+`cacheVersion` moved from v257 to v265, so caches rebuild once and a pinned
+baseline can show a one-time change.
+
+The vendored Prism provider script is re-vendored from v0.4.19. It had stayed
+at provider version 0.1.0, the v0.4.4 script, while upstream moved it to 0.2.0
+in 0.4.5: the seam hands the script a `--files` listing of the paths it holds
+no cache entry for, and the 0.1.0 script parsed the whole tree regardless. The
+Rubydex engine pin is unchanged at 0.4.0, which is what 0.4.19 fetches.
+
+munola 0.6.3 drives channel release `0.4.19.1`, cut from the promoted current
+at upstream enola 0.4.19. Three changes promoted into the channel after
+0.4.10.1 ship for the first time: `enola check -member` grades one repository
+of a multi-repository config against the union pin by replaying it, a
+constraints sentence written in snake_case reaches a recipe published in
+kebab-case, and the module-edges binder keys symbol placement by repository
+and drops its own prior derivations before deriving. Still carried: the
+recipe catalogue at enola-guides v0.3.1, the init role binding, the
+cache-version double history at cacheVersion v265, and the blame.go
+spelling. The config munola writes also stops naming the Prism provider's
+version as a fixed `0.1.0`; it asks the script, as the enola gem's config
+already did.
+
+## 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

data/README.md

@@ -13,7 +13,7 @@ because nobody installs it to avoid Rails. The Rails code is written once, in
 ## `enola`
 
 The wrapper of the released enola. The gem versions itself; the release it
-drives is `Enola::UPSTREAM_VERSION`, v0.4.4 as of `enola 0.5.0`, and every
+drives is `Enola::UPSTREAM_VERSION`, v0.4.19 as of `enola 0.5.5`, and every
 gemspec summary names it.
 
 ```ruby
@@ -29,7 +29,7 @@ bundle exec enola check .
 The first command that needs the binary downloads the release for your
 platform (linux, darwin, windows; amd64, arm64), verifies it against the
 sha256 file the same release publishes, and keeps it under
-`~/.cache/enola/upstream/0.4.4/` (`ENOLA_CACHE_DIR` moves the root). An
+`~/.cache/enola/upstream/0.4.19/` (`ENOLA_CACHE_DIR` moves the root). An
 `enola` already on your PATH is used only when it answers the pinned version;
 offline with an empty cache is a refusal that names the cache and the release
 rather than a fallback to whatever is installed. Nothing downloads at

data/lib/munola/providers_config.rb

@@ -23,7 +23,7 @@ module Munola
       lines = ["repo: .", "repos:", "  - .", "providers:"]
       script = prism_script
       if script
-        lines += ["  - name: prism", "    command: [#{ruby.inspect}, #{script.inspect}]", "    expected_version: \"0.1.0\""]
+        lines += ["  - name: prism", "    command: [#{ruby.inspect}, #{script.inspect}]", "    expected_version: #{prism_version.inspect}"]
       else
         lines << "  # prism: the enola gem on this machine carries no provider script; add one here to run it"
       end
@@ -31,6 +31,11 @@ module Munola
       "#{lines.join("\n")}\n"
     end
 
+    def self.prism_version
+      version = Enola::Providers.prism_version if Enola::Providers.respond_to?(:prism_version)
+      version || "0.2.0"
+    end
+
     def self.prism_script
       return nil unless defined?(Enola::Providers) && Enola::Providers.respond_to?(:prism_script)
 

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.6"
-  CHANNEL_VERSION = "0.4.6.1"
-  VERSION = "0.6.1"
+  UPSTREAM_VERSION = "0.4.19"
+  CHANNEL_VERSION = "0.4.19.1"
+  VERSION = "0.6.3"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: munola
 version: !ruby/object:Gem::Version
-  version: 0.6.1
+  version: 0.6.3
 platform: ruby
 authors:
 - Muhamed Isabegovic
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2026-08-24 00:00:00.000000000 Z
+date: 2026-09-14 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.6.1, built on enola
-  0.4.6. Everything else is the enola gem's wrapper,
+  gem drives channel release 0.4.19.1, built on enola
+  0.4.19. 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.