enola 0.4.4.1 → 0.5.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 84ee668ecfaed2e6d8ebc55fe5054e1635300502f762887f2d7b96660beb908f
-  data.tar.gz: 2905c89cad26afb7f6226515c7b3620ed6e089c16ff5886398f4043deda50360
+  metadata.gz: 689fed2c591f5809d780118557d16abb71dd2c16ae81e71382fbeee1cb70001e
+  data.tar.gz: c7c4671e4d4c153f8f0f6db9f9395a6670681a1006581c5faecf2b196170cc30
 SHA512:
-  metadata.gz: e8b8a19a54c9f13be8b2dd6a1d62b5cb999d14a7ff959f0771ca25cfc63b6fac3822bc31ccd676cc44c60e4106401c626f9fc1e7b2802a68d3f5f68a0c23c322
-  data.tar.gz: 42a9119e1b7d33d1a20b3e3d9f7a79f2c8199de3599365f6d13674db19a968aba0a749180014b061bb413940a17ae8212ebf63181ee40302acdcae20952c1bb5
+  metadata.gz: b4a72e0931b1f110f482062fa8e2627f59adfac7add1592ea1c8ef22e5bc4f6f7fc5c4ae851cf7534c50997ec8fc3cd2928e3e84a0e3bc841f9f22ee87933d85
+  data.tar.gz: 7f5cd2dc8f9b69897c095c54e95d4c9d58913607de47ca71789fa3eb8d419811d5d2c5393cc6abed7630e2f35314b6c76b61836beff63fa012761eaa0f27c4e7

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

@@ -11,8 +11,9 @@ 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"
@@ -44,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.
 
@@ -73,10 +74,10 @@ 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"
@@ -99,18 +100,19 @@ 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 its upstream
-version and on `enola-guides` 0.3.1 or later; requiring it loads no Rails.
+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 their own versions and adds one generator.
+both at the same minor and adds one generator.
 
 ```ruby
 gem "munola-rb"

data/lib/enola/version.rb

@@ -1,8 +1,8 @@
 # frozen_string_literal: true
 
 module Enola
-  # The release this wrapper drives. VERSION carries a patch segment for
-  # wrapper-only fixes, so what to fetch is stated separately.
+  # The gem versions itself. UPSTREAM_VERSION names the enola release it
+  # fetches and drives.
   UPSTREAM_VERSION = "0.4.4"
-  VERSION = "#{UPSTREAM_VERSION}.1"
+  VERSION = "0.5.0"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: enola
 version: !ruby/object:Gem::Version
-  version: 0.4.4.1
+  version: 0.5.0
 platform: ruby
 authors:
 - Muhamed Isabegovic
@@ -26,8 +26,9 @@ dependencies:
         version: '1.3'
 description: |
   A pure-Ruby wrapper around enola, the architecture-graph tool by enola-labs.
-  The gem's version is the upstream release it drives. The binary is not in
-  the gem: the first command that needs it downloads the release for your
+  The gem versions itself; the enola release it drives is named in its
+  UPSTREAM_VERSION, 0.4.4 here. The binary is not in the
+  gem: the first command that needs it downloads the release for your
   platform, verifies it against the checksum the release publishes, and keeps
   it in a per-user cache. Every command and exit code is forwarded unchanged.
   This gem is not an enola-labs release.
@@ -79,6 +80,6 @@ requirements: []
 rubygems_version: 3.5.22
 signing_key:
 specification_version: 4
-summary: 'Runs the released enola from Ruby: fetched on first use, verified, pinned
-  to this gem''s version.'
+summary: 'Runs the released enola from Ruby: fetched on first use, verified, cached.
+  This release drives enola 0.4.4.'
 test_files: []