enola-rb 0.5.5 → 0.5.6

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 6f347bb5efb06ec6100e263dc969771c5c4f63acf0da1e7ea28f1e37e0be08c6
4
- data.tar.gz: 30bc11ebdd54f53b3e44630c12103c7d4414f9864abd1afa0858f7f622962adb
3
+ metadata.gz: fc6eb32e2f842b6863c489ecf01ebee56294db5c02248bad8749c03125d6dade
4
+ data.tar.gz: 50d451e646defb07ebffe1afeb102cd0088988fdab2b9c9b84411c477ab6107d
5
5
  SHA512:
6
- metadata.gz: 6b8c5e4178b8e5e2d58c4dc42f4513a94d701b071e0f08527feea445d6c927db44b8cae23981bd0a14fc83cad4487039e427a27c8917b3b01ad52cabe2a46be9
7
- data.tar.gz: 9150913383a53a4cd77d50637d971f24f57b1ca3d618b0ddca083e3bb71acb683bee86dbbf2959cd42f0a513e4c27171920ac4a839fe52571f569403c4e784c9
6
+ metadata.gz: 466e121b7d0294bcafd5aae0da2d9e1b3166949eda4c011141c22a4f506f7d98a8094bc38091c6962e5783a3a182851c69ef48461610a43b48f6da1f5f7a0e25
7
+ data.tar.gz: b03f0e46f45b4f5051616c0e14e35ded51e73ce3c70a8d91e54b05767edee0409baf5e1afab77aec3e821915ab40c0ab7751bea0ea38b952f910496d765c3227
data/CHANGELOG.md CHANGED
@@ -1,3 +1,28 @@
1
+ ## enola 0.5.6 and enola-rb 0.5.6 (2026-10-20)
2
+
3
+ The enola and enola-rb gems drive upstream enola 0.4.32. Between 0.4.19 and
4
+ here upstream indexed a folder of repositories as a cluster (0.4.20), took dead
5
+ code, performance and package metrics into enola itself (0.4.21), installed as
6
+ a Claude Code plugin (0.4.22), stopped counting loops that cannot grow (0.4.23),
7
+ read FastAPI routes in every registration form (0.4.24), parsed Scala 3
8
+ capture-checked code (0.4.25), linked a cross-repo call to the function making
9
+ it and the one serving it (0.4.26), answered `enola impact` from the command
10
+ line (0.4.27), rested performance findings on facts about the callee (0.4.28),
11
+ walked a Laravel endpoint from its URL to its tables (0.4.29), added `enola
12
+ flows` and a `doc` prop on symbols (0.4.30), bound more routes to their
13
+ handlers and extracted TypeScript about twice as fast (0.4.31), and read docs
14
+ from comments in ten languages, module docs from package comments among them,
15
+ with a `docs.jsonl` renderer on by default (0.4.32). `cacheVersion` moved from v265 to v390, so caches rebuild
16
+ once and a pinned baseline can show a one-time change.
17
+
18
+ The vendored Prism provider script is re-vendored from v0.4.32. Its body is
19
+ unchanged since v0.4.19 and it still answers provider version 0.2.0; only the
20
+ line naming where it was vendored from moves. The Rubydex engine pin is
21
+ unchanged at 0.4.0, which is what 0.4.32 fetches.
22
+
23
+ munola is unchanged and still drives channel release `0.4.19.1`, until the
24
+ channel is cut on 0.4.32.
25
+
1
26
  ## enola 0.5.5, enola-rb 0.5.5 and munola 0.6.3 (2026-09-14)
2
27
 
3
28
  The enola and enola-rb gems drive upstream enola 0.4.19. Between 0.4.10 and
data/README.md CHANGED
@@ -13,7 +13,7 @@ because nobody installs it to avoid Rails. The Rails code is written once, in
13
13
  ## `enola`
14
14
 
15
15
  The wrapper of the released enola. The gem versions itself; the release it
16
- drives is `Enola::UPSTREAM_VERSION`, v0.4.19 as of `enola 0.5.5`, and every
16
+ drives is `Enola::UPSTREAM_VERSION`, v0.4.32 as of `enola 0.5.6`, and every
17
17
  gemspec summary names it.
18
18
 
19
19
  ```ruby
@@ -29,7 +29,7 @@ bundle exec enola check .
29
29
  The first command that needs the binary downloads the release for your
30
30
  platform (linux, darwin, windows; amd64, arm64), verifies it against the
31
31
  sha256 file the same release publishes, and keeps it under
32
- `~/.cache/enola/upstream/0.4.19/` (`ENOLA_CACHE_DIR` moves the root). An
32
+ `~/.cache/enola/upstream/0.4.32/` (`ENOLA_CACHE_DIR` moves the root). An
33
33
  `enola` already on your PATH is used only when it answers the pinned version;
34
34
  offline with an empty cache is a refusal that names the cache and the release
35
35
  rather than a fallback to whatever is installed. Nothing downloads at
@@ -1,5 +1,5 @@
1
1
  # frozen_string_literal: true
2
2
 
3
3
  module EnolaRb
4
- VERSION = "0.5.5"
4
+ VERSION = "0.5.6"
5
5
  end
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: enola-rb
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.5.5
4
+ version: 0.5.6
5
5
  platform: ruby
6
6
  authors:
7
7
  - Muhamed Isabegovic
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2026-09-14 00:00:00.000000000 Z
11
+ date: 2026-10-20 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: enola