munola 0.6.0 → 0.6.1

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: 558cd383ea993d03a3a667a3287a7ae27db1f8a41642e63bce0727846a1af987
4
- data.tar.gz: 5cd95dccec42025f8cea27b8b6aaa528f8a1f7e4b17ddb1be53541a12bf62268
3
+ metadata.gz: 035c3780ee982f7ae5ec0dc3613ae0d09d4e7ae6fc1a6c3bbe7d446da45548b5
4
+ data.tar.gz: 7f17a853e60b770fe08a90f9f055f1891f1c3f7d7a59c188ba44e8e0744a3d10
5
5
  SHA512:
6
- metadata.gz: 2a47d2376487ef8e19cf22b5f66d00f32eb1ab8e7cab3750846ccc048a6739ec5cd7f6f4e7a527079a7c5ca3555baeb5d2ac7cf9000c2aa4ed772e225d30be0b
7
- data.tar.gz: 51e549f4e966e6ad231f7618c2b9e7826a84fa0b2c8972c3fd35ff666128bfdf2d0f2b9fda657139b1548ac2ae9a2f76c138e75e8c178a9ebc95f9aa3a7c5ccb
6
+ metadata.gz: a50a5ba6d22316da864d6a1c15b5eee82a681e9e87d7de00590a211453ec7fa512cd6fae628ee94e800977f46a18e26201ffc5f4f98a8f7a537586e6fb7f96e7
7
+ data.tar.gz: 0c07b025c1f109e040f3af93de83be72e84b34de591956d95a1b91a25bd1daf7cbdaae9dbbc8fb49fc777d956dec5c0e64b010311e447dbafcf0cd20b8af325a
data/CHANGELOG.md CHANGED
@@ -1,3 +1,21 @@
1
+ ## munola 0.6.1 (2026-08-24)
2
+
3
+ munola drives channel release `0.4.6.1`, cut from the promoted current at
4
+ upstream enola 0.4.6. The prefix walk fix is in the binary this gem fetches,
5
+ so the expiry the 0.6.0 note named is met and Rubydex is on by default again.
6
+ The channel still carries the exclusion filter, which upstream merged an hour
7
+ after 0.4.6 was published, so an excluded document is skipped before its
8
+ definitions are read: 440 seconds to 193 on a Rails monolith, facts identical.
9
+
10
+ The 0.6.0 note said munola waits on Prism alone. On the Rails install path it
11
+ did not. `munola init` reuses enola-rb's installer, which writes
12
+ `mcp-arch.yaml` first, and munola's own writer yields to a file that already
13
+ exists, so the config every Rails project got was the enola gem's, with both
14
+ providers on, against a channel binary built before the fix. Two things follow.
15
+ The config and the binary now agree, which is what closes it. And munola's
16
+ writer has a test that reads munola's writer, rather than one that reads the
17
+ file enola-rb wrote and reports on munola.
18
+
1
19
  ## enola 0.5.3, enola-rb 0.5.3 and munola 0.6.0 (2026-08-24)
2
20
 
3
21
  Both providers are on again. enola-labs shipped the prefix walk fix in 0.4.6,
@@ -27,10 +27,7 @@ module Munola
27
27
  else
28
28
  lines << " # prism: the enola gem on this machine carries no provider script; add one here to run it"
29
29
  end
30
- lines += [" # rubydex is off until the channel release carries the walk fix:",
31
- " # a reference spanning lines could be its own predecessor, so a tree with",
32
- " # vendored gems could snapshot without ever finishing. Uncomment to run it.",
33
- " # - name: rubydex", " # expected_version: \"#{RUBYDEX_VERSION}\""]
30
+ lines += [" - name: rubydex", " expected_version: \"#{RUBYDEX_VERSION}\""]
34
31
  "#{lines.join("\n")}\n"
35
32
  end
36
33
 
@@ -3,7 +3,7 @@
3
3
  module Munola
4
4
  # UPSTREAM_VERSION names the enola release this channel is built on,
5
5
  # CHANNEL_VERSION the fork release the gem fetches.
6
- UPSTREAM_VERSION = "0.4.4"
7
- CHANNEL_VERSION = "0.4.4.2"
8
- VERSION = "0.6.0"
6
+ UPSTREAM_VERSION = "0.4.6"
7
+ CHANNEL_VERSION = "0.4.6.1"
8
+ VERSION = "0.6.1"
9
9
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: munola
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.6.0
4
+ version: 0.6.1
5
5
  platform: ruby
6
6
  authors:
7
7
  - Muhamed Isabegovic
@@ -56,8 +56,8 @@ description: |
56
56
  The binary this gem fetches is not an enola-labs release. It is a build
57
57
  cut from https://github.com/misabegovic/enola, a fork of enola, whose
58
58
  release notes name what differs from upstream release by release; this
59
- gem drives channel release 0.4.4.2, built on enola
60
- 0.4.4. Everything else is the enola gem's wrapper,
59
+ gem drives channel release 0.4.6.1, built on enola
60
+ 0.4.6. Everything else is the enola gem's wrapper,
61
61
  unchanged: fetched on first use, verified against the checksums the
62
62
  release publishes, cached per user, every command and exit code
63
63
  forwarded. Use the enola gem to run stock upstream instead.