munola 0.4.4.1 → 0.5.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: fc1f44ab0b5e72d5f18dda2afe879b156a0b9ac9a0ae337a1419b3641d2e91a1
-  data.tar.gz: d3f40bfc7e5c2225a268c025ef8a5ab4d141cc3109d1e0faa79c05d7204b210f
+  metadata.gz: 3fef04df27a6176d9c98ef6a96588ab444f63e92a6ef3c3c3fd73268af931de3
+  data.tar.gz: 8190ecb25656352775ea9ead33c18e04c7faddaac23d67644045398fea80ce26
 SHA512:
-  metadata.gz: 7401c008c0765293332500601bcb0243342f04e36f8332a4ca48a9f0de72525677b22aea0b1accb83989bcd8c072e70f114531c746057fd5e8a4e7288f139ef8
-  data.tar.gz: 5d91e09afc035996dfca5798b73f16f93cd4effad7a70b3da65dc919509892c5794b2dce05be6f9147e253bc02af125da98dd0ef45912ce507b5f2103f406d12
+  metadata.gz: 7524cf02ef40ba7136a5ff531ffda09c2e1056b9a53b73710728be0ad64a7158d3aeccf94492a7401619776d2a44a07e22bcff7511ac775083112de200df4820
+  data.tar.gz: fcf9fc3d4ac887817ad8dab39f5c071d4569a282a12fa2720bd5f935da62a4793e6a833c45032cead51f653603baf675f78f2f064351a8bae23516f912a9e883

data/CHANGELOG.md

@@ -1,3 +1,34 @@
+## 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
+channel after it took eight changes measured against a Ruby architecture
+linter, so the gem's version moves with the release it fetches. The Rails
+layer is its own gem, `munola-rb`, the way `enola-rb` is for the upstream
+channel; `require "munola"` loads no Rails. A catalogue recipe the binary
+already binds is no longer bound a second time.
+
+## enola 0.4.4.1 and enola-rb 0.4.4.1 (2026-08-23)
+
+Wrapper fixes on the same upstream release. A test that set the channel put
+back upstream rather than what it found, so on some orderings a channel gem's
+own installation read as upstream. The Rails layer packaged its generator
+through a glob wide enough to take another channel's; it now packages its own.
+Both gems still drive upstream v0.4.4.
+
+## munola-rb 0.4.4.1 (2026-08-23)
+
+The Rails layer over munola, what enola-rb is to enola: `rails generate
+munola:install [--tenant-column COLUMN]` writes the starter laws, the
+bindings the binary's own init picks and the munola catalogue, and the
+enola:init, enola:snapshot and enola:check tasks drive munola's binary
+because munola installs its own resolver. The generator and the railtie
+move here out of the munola gem, so `require "munola"` loads no Rails and a
+project that only drives the binary carries no Rails machinery. The recipe
+catalogue, the detection and the tenant-column argument stay munola's.
+
+`Enola.resolver_factory` is readable as well as writable, so whoever
+replaces it can put back what was installed rather than what it assumed.
+
 ## munola 0.4.4.1 (2026-08-23)
 
 The wrapper over the munola channel, first release with an implementation.

data/LICENSE

@@ -187,7 +187,7 @@ APPENDIX: How to apply the Apache License to your work.
   same "printed page" as the copyright notice for easier
   identification within third-party archives.
 
-Copyright (c) 2026 Dejan Menges
+Copyright (c) 2026 Muhamed Isabegovic
 
 Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.

data/README.md

@@ -1,13 +1,19 @@
 # enola-rb
 
-Three pure-Ruby gems, one repository, for running
+Four pure-Ruby gems, one repository, for running
 [enola](https://github.com/enola-labs/enola), the architecture-graph tool,
 from Ruby. None of them carries a binary or compiles anything.
 
+Two channels, the same layering on both: `enola` wraps the released upstream
+binary and `enola-rb` adds the Rails layer on it; `munola` wraps the munola
+binary and `munola-rb` adds the Rails layer on that. The Rails code is written
+once, in `enola-rb`, and the munola gems add only what is munola's own.
+
 ## `enola`
 
-The wrapper of the released enola. Its version is the upstream release it
-drives: `enola 0.4.4` runs enola-labs' v0.4.4.
+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
+gemspec summary names it.
 
 ```ruby
 gem "enola"
@@ -39,7 +45,7 @@ This gem is not an enola-labs release; it runs theirs.
 
 ## `enola-rb`
 
-The Rails layer over `enola`. It depends on `enola` at the same version and on
+The Rails layer over `enola`. It depends on `enola` at the same minor and on
 [enola-guides](https://github.com/misabegovic/enola-guides), and adds nothing
 to the binary's surface.
 
@@ -68,18 +74,17 @@ remedy.
 
 One person's taste on top of enola: the same wrapper over another channel,
 the builds cut from [a fork of enola](https://github.com/misabegovic/enola),
-versioned as the upstream they are built on plus a fourth segment
-(`0.4.4.1` drives a build on v0.4.4), each release naming what differs from
-that upstream. It is offered upstream where it fits and is not positioned
-against it. What it adds is the channel and the catalogue.
+each release naming what differs from that upstream. The gem versions itself;
+the channel release it fetches is `Munola::CHANNEL_VERSION`, which carries the
+upstream it is built on plus a segment of its own (`0.4.4.2` on v0.4.4). It is
+offered upstream where it fits and is not positioned against it. What it adds is the channel and the catalogue.
 
 ```ruby
 gem "munola"
 ```
 
 ```sh
-bin/rails generate munola:install --tenant-column company_id
-bundle exec munola init .
+bundle exec munola init . --tenant-column company_id
 bundle exec munola --version
 ```
 
@@ -95,9 +100,31 @@ inflection table; it writes `mcp-arch.yaml` with both Ruby providers on by
 default, Prism through the script the `enola` gem carries and Rubydex built
 into the binary, and fetches the Rubydex library, a failed fetch reported as a
 named skip. It never asks a question. `munola --version` names the munola
-version, the upstream it is built on and which binary answered.
+version, the channel release and upstream it is built on, and which binary
+answered.
+
+The binary comes from the fork's releases the way `enola`'s comes from
+upstream's, fetched on first use and verified against the sha256 the release
+publishes; `MUNOLA_BINARY=/path/to/enola` names one to drive instead, and
+every command says which answered. `munola` depends on `enola` at the same
+minor and on `enola-guides` 0.3.1 or later; requiring it loads no Rails.
+
+## `munola-rb`
+
+The Rails layer over `munola`, what `enola-rb` is to `enola`. It depends on
+both at the same minor and adds one generator.
+
+```ruby
+gem "munola-rb"
+```
+
+```sh
+bin/rails generate munola:install --tenant-column company_id
+bin/rake enola:snapshot
+bin/rake enola:check
+```
 
-The first munola release is what makes the channel real; until it is cut,
-`MUNOLA_BINARY=/path/to/enola` names the binary to drive, and every command
-says so. `munola` depends on `enola` and `enola-rb` at its upstream version
-and on `enola-guides` 0.3.1 or later.
+The generator runs the same install `munola init` does. The rake tasks are
+enola-rb's and need no munola copy: `munola` installs its own resolver when it
+loads, so `enola:snapshot` and `enola:check` drive the munola binary in an app
+that has this gem, and the upstream binary in one that does not.

data/lib/munola/catalogue.rb

@@ -12,6 +12,7 @@ module Munola
     PLACEHOLDERS = { column: "TENANT_COLUMN", table: "TENANT_TABLE" }.freeze
 
     def self.source_dir
+      require "enola-rb"
       File.join(EnolaRb::Guides.root, "recipes")
     end
 

data/lib/munola/channel.rb

@@ -4,7 +4,7 @@ module Munola
   CHANNEL = Enola::Channel.new(
     name: "munola",
     release_base: "https://github.com/misabegovic/enola/releases/download",
-    version: VERSION,
+    version: CHANNEL_VERSION,
     asset_prefix: "enola",
     tag_prefix: "munola-v"
   ).freeze
@@ -32,6 +32,6 @@ module Munola
   end
 
   def self.channel_line(found = resolve)
-    "munola #{VERSION}, built on enola #{UPSTREAM_VERSION}; binary via #{found.source} (#{found.path})"
+    "munola #{VERSION}, channel #{CHANNEL_VERSION} on enola #{UPSTREAM_VERSION}; binary via #{found.source} (#{found.path})"
   end
 end

data/lib/munola/installer.rb

@@ -26,7 +26,11 @@ module Munola
     # The Rails layer first (starter laws, the binary's own init, upstream's
     # recipes commented), then what only munola carries: the catalogue, the
     # bindings the tree justifies, the providers both on by default.
+    # enola-rb carries the installer this reuses; it is required here rather
+    # than at load time so `require "munola"` stays a wrapper and pulls in no
+    # Rails machinery for a project that only drives the binary.
     def install
+      require "enola-rb"
       rails = EnolaRb::Installer.new(@root, binary: resolved_binary, stderr: @stderr).install
       @report.written.concat(rails.written)
       @report.notes.concat(rails.notes)
@@ -55,6 +59,10 @@ module Munola
       File.join(@root, "enola", "constraints", "recipes.yaml")
     end
 
+    # A munola binary carries the catalogue itself, so its own `constraints
+    # init` may already have bound a recipe this would bind again, and two
+    # instances of one recipe expand to colliding rule ids. What the file
+    # already names is left alone and counted as bound.
     def bind(names)
       @bound = names & Catalogue::RECIPES
       @commented = Catalogue::RECIPES - @bound
@@ -62,7 +70,8 @@ module Munola
       return if existing.include?("# munola catalogue")
 
       doc = YAML.safe_load(existing) || {}
-      entries = Array(doc["use_recipe"]) + @bound.map { |name| { "recipe" => name, "as" => name, "mode" => "advisory" } }
+      declared = Array(doc["use_recipe"]).map { |entry| entry["recipe"] }.compact
+      entries = Array(doc["use_recipe"]) + (@bound - declared).map { |name| { "recipe" => name, "as" => name, "mode" => "advisory" } }
       body = YAML.dump({ "use_recipe" => entries }).sub(/\A---\n/, "")
       tail = existing[/\n# Shipped recipes not bound.*\z/m].to_s
       commented = @commented.map { |name| "#  - recipe: #{name}\n#    as: #{name}\n#    mode: advisory\n" }.join

data/lib/munola/version.rb

@@ -1,6 +1,9 @@
 # frozen_string_literal: true
 
 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"
-  VERSION = "#{UPSTREAM_VERSION}.1"
+  CHANNEL_VERSION = "0.4.4.2"
+  VERSION = "0.5.0"
 end

data/lib/munola.rb

@@ -1,7 +1,6 @@
 # frozen_string_literal: true
 
 require "enola"
-require "enola-rb"
 require_relative "munola/version"
 require_relative "munola/channel"
 require_relative "munola/catalogue"
@@ -9,7 +8,6 @@ require_relative "munola/detector"
 require_relative "munola/providers_config"
 require_relative "munola/installer"
 require_relative "munola/cli"
-require_relative "munola/railtie" if defined?(Rails::Railtie)
 
 Enola.channel = Munola::CHANNEL
 Enola.resolver_factory = -> { Munola::Resolver.new(channel: Munola::CHANNEL) }

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: munola
 version: !ruby/object:Gem::Version
-  version: 0.4.4.1
+  version: 0.5.0
 platform: ruby
 authors:
 - Muhamed Isabegovic
@@ -14,30 +14,30 @@ dependencies:
   name: enola
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - '='
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.4.4
+        version: 0.5.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - '='
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.4.4
+        version: 0.5.0
 - !ruby/object:Gem::Dependency
   name: enola-rb
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - '='
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.4.4
+        version: 0.5.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - '='
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.4.4
+        version: 0.5.0
 - !ruby/object:Gem::Dependency
   name: enola-guides
   requirement: !ruby/object:Gem::Requirement
@@ -54,13 +54,13 @@ dependencies:
         version: 0.3.1
 description: |
   The same pure-Ruby wrapper as the enola gem over another channel: the
-  builds cut from a fork of enola, versioned as the upstream they are built
-  on plus a fourth segment, each release naming what differs. `munola init`
-  writes the recipe catalogue the enola-guides gem carries (Ember, data
-  ownership, API boundaries, background work, a tenant foreign key) into
-  the project and binds the recipes its tree justifies, and turns both Ruby
-  providers on by default. Offered upstream where it fits; no binary here,
-  nothing compiled.
+  builds cut from a fork of enola, each release naming what differs. This
+  gem drives channel release 0.4.4.2, built on enola
+  0.4.4. `munola init` writes the recipe catalogue the
+  enola-guides gem carries (Ember, data ownership, API boundaries,
+  background work, a tenant foreign key) into the project and binds the
+  recipes its tree justifies, and turns both Ruby providers on by default. The Rails generator lives in munola-rb. Offered
+  upstream where it fits; no binary here, nothing compiled.
 email:
 - m.isabegovic@hotmail.com
 executables:
@@ -72,7 +72,6 @@ files:
 - LICENSE
 - README.md
 - exe/munola
-- lib/generators/munola/install/install_generator.rb
 - lib/munola.rb
 - lib/munola/catalogue.rb
 - lib/munola/channel.rb
@@ -80,7 +79,6 @@ files:
 - lib/munola/detector.rb
 - lib/munola/installer.rb
 - lib/munola/providers_config.rb
-- lib/munola/railtie.rb
 - lib/munola/version.rb
 homepage: https://github.com/misabegovic/enola-rb
 licenses:

data/lib/generators/munola/install/install_generator.rb

@@ -1,19 +0,0 @@
-# frozen_string_literal: true
-
-require "rails/generators"
-require "munola"
-
-module Munola
-  module Generators
-    class InstallGenerator < Rails::Generators::Base
-      desc "Writes enola/constraints/ and the munola recipe catalogue, binding what the tree shows a need for"
-      class_option :tenant_column, type: :string, default: nil, desc: "The column most tables carry; confirmed against db/schema.rb"
-
-      def install
-        Munola::Installer.new(destination_root, tenant_column: options[:tenant_column]).install.lines.each { |line| say line }
-      rescue Enola::Error => e
-        raise Thor::Error, "munola: #{e.message}"
-      end
-    end
-  end
-end

data/lib/munola/railtie.rb

@@ -1,7 +0,0 @@
-# frozen_string_literal: true
-
-module Munola
-  class Railtie < Rails::Railtie
-    generators { require_relative "../generators/munola/install/install_generator" }
-  end
-end