enola-rb 0.5.3 → 0.5.4
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 +4 -4
- data/CHANGELOG.md +29 -0
- data/lib/enola_rb/version.rb +1 -1
- metadata +2 -2
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 0bb6257fb13895fde285429aaf5db998032bccabb36f4656be7a6331ecb53104
|
|
4
|
+
data.tar.gz: 18ae2893b61aa9dd44efe829715e12fd9d72a47d391031b3004368d9bb7090db
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 2b3f8562c158c7f5fd506bf3c837382eb529fef8f28b89c74e258ed43aabdb1c0590ae889f1f152dbe28c604d8c24f60e109ba92154b9dd92155b62e14f0318e
|
|
7
|
+
data.tar.gz: a3486dce7c6494142e3c45a681c96f02b2ed270e5570010cd86bc0e47ad861750b74329738f566f7e4ace81b5814f9672258756ef3f23a9ecd4b79d85fc927b2
|
data/CHANGELOG.md
CHANGED
|
@@ -1,3 +1,32 @@
|
|
|
1
|
+
## enola 0.5.4 and enola-rb 0.5.4 (2026-08-30)
|
|
2
|
+
|
|
3
|
+
The gems drive upstream enola 0.4.10. Between 0.4.6 and here upstream took the
|
|
4
|
+
exclusion filter (#255, in 0.4.7), rescored the layers explainer per language
|
|
5
|
+
cohort (0.4.7), began reading package manifests as dependency facts with a
|
|
6
|
+
declared-purpose diff (0.4.8), gave the dashboard its own command (0.4.9), and
|
|
7
|
+
documented the snapshot artifacts as a versioned contract with fact identity
|
|
8
|
+
(0.4.10). The vendored Prism provider script and the Rubydex engine pin are
|
|
9
|
+
byte-identical across the span, so nothing re-vendors; the wrappers move by
|
|
10
|
+
the release they name.
|
|
11
|
+
|
|
12
|
+
## munola 0.6.1 (2026-08-24)
|
|
13
|
+
|
|
14
|
+
munola drives channel release `0.4.6.1`, cut from the promoted current at
|
|
15
|
+
upstream enola 0.4.6. The prefix walk fix is in the binary this gem fetches,
|
|
16
|
+
so the expiry the 0.6.0 note named is met and Rubydex is on by default again.
|
|
17
|
+
The channel still carries the exclusion filter, which upstream merged an hour
|
|
18
|
+
after 0.4.6 was published, so an excluded document is skipped before its
|
|
19
|
+
definitions are read: 440 seconds to 193 on a Rails monolith, facts identical.
|
|
20
|
+
|
|
21
|
+
The 0.6.0 note said munola waits on Prism alone. On the Rails install path it
|
|
22
|
+
did not. `munola init` reuses enola-rb's installer, which writes
|
|
23
|
+
`mcp-arch.yaml` first, and munola's own writer yields to a file that already
|
|
24
|
+
exists, so the config every Rails project got was the enola gem's, with both
|
|
25
|
+
providers on, against a channel binary built before the fix. Two things follow.
|
|
26
|
+
The config and the binary now agree, which is what closes it. And munola's
|
|
27
|
+
writer has a test that reads munola's writer, rather than one that reads the
|
|
28
|
+
file enola-rb wrote and reports on munola.
|
|
29
|
+
|
|
1
30
|
## enola 0.5.3, enola-rb 0.5.3 and munola 0.6.0 (2026-08-24)
|
|
2
31
|
|
|
3
32
|
Both providers are on again. enola-labs shipped the prefix walk fix in 0.4.6,
|
data/lib/enola_rb/version.rb
CHANGED
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.
|
|
4
|
+
version: 0.5.4
|
|
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-08-
|
|
11
|
+
date: 2026-08-30 00:00:00.000000000 Z
|
|
12
12
|
dependencies:
|
|
13
13
|
- !ruby/object:Gem::Dependency
|
|
14
14
|
name: enola
|