gemvault 0.3.0 → 0.3.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 +4 -4
- data/CHANGELOG.md +4 -2
- data/CLAUDE.md +5 -0
- data/Dockerfile.test +2 -2
- data/README.md +5 -2
- data/lib/gemvault/version.rb +1 -1
- metadata +1 -1
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 94a4a1ec7a201451cc0d20c7dafda3b0cbdd3f6456e89a4e5a610fd6dac1d140
|
|
4
|
+
data.tar.gz: 2289af90f2cb6fa5dedbb3e1005d8856d1236147412ac415be9bf7da5c239e50
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 41e777197f5ec6c540353b4df4595e361b2cd351519f0c2fb0d9c1db443091ff983f5a6709405f3b241f460320f9ab12a22f89cd1b03daf4882639117b811c6e
|
|
7
|
+
data.tar.gz: 05aa3c5ef0ee2fb4b7d85418d1b95d95065f688c25ec4e624fa35383b9426a07bc049a8a81cf028b602d38d80e3e355a21bc334a4de3cca9688bd645cc6098fe
|
data/CHANGELOG.md
CHANGED
|
@@ -33,6 +33,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|
|
33
33
|
is shared with the RubyGems source via `Gemvault::VaultPath` (issue #9).
|
|
34
34
|
|
|
35
35
|
### Fixed
|
|
36
|
+
- The plugin loads again on Bundler older than 4.1.0. 0.3.0 refused to, and
|
|
37
|
+
because Bundler installs the newest plugin for a `type: :vault` source, that
|
|
38
|
+
broke every fresh install of such a bundle on an older Bundler. An addressed vault still needs
|
|
39
|
+
Bundler 4.1.0.
|
|
36
40
|
- `gemvault doctor` now repairs ghost installations: a
|
|
37
41
|
`specifications/<gem>-<version>.gemspec` left behind after its gem directory
|
|
38
42
|
was removed (interrupted uninstall, hand-cleaned gem home), even when the
|
|
@@ -113,8 +117,6 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|
|
113
117
|
gemvault through `require_relative` alone (issue #13).
|
|
114
118
|
|
|
115
119
|
### Changed
|
|
116
|
-
- `bundler-source-vault` requires Bundler 4.1.0 or newer and refuses to load on
|
|
117
|
-
an older one, for `type: :vault` as well as for addressed vaults.
|
|
118
120
|
- With Bundler 4.1.0 a project that sets `path` cannot take the plugin from
|
|
119
121
|
system gems: Bundler applies `path` before it resolves Gemfile plugins, so
|
|
120
122
|
the Gemfile needs a gem index that carries `bundler-source-vault`.
|
data/CLAUDE.md
CHANGED
|
@@ -35,6 +35,11 @@ with a clear message instead of degrading silently, and prefer the simpler
|
|
|
35
35
|
design over one that keeps an old path alive. Anyone who needs compatibility
|
|
36
36
|
uses an earlier version of the gem and of Bundler.
|
|
37
37
|
|
|
38
|
+
One exception: the plugin must always load on an older Bundler. Bundler
|
|
39
|
+
installs the newest plugin for a `type: :vault` source on every fresh install,
|
|
40
|
+
so a plugin that refuses to load breaks those bundles the moment it is
|
|
41
|
+
published. Gate the feature that needs the newer Bundler, never the load.
|
|
42
|
+
|
|
38
43
|
## Project Overview
|
|
39
44
|
|
|
40
45
|
Multi-gem portable archives. A single `.gemv` file is a tarball holding multiple `.gem` files plus a line-oriented `manifest` index; legacy SQLite vaults are read-only.
|
data/Dockerfile.test
CHANGED
|
@@ -24,8 +24,8 @@ RUN dnf \
|
|
|
24
24
|
sqlite3 \
|
|
25
25
|
&& dnf clean all
|
|
26
26
|
|
|
27
|
-
# The oldest Bundler
|
|
28
|
-
#
|
|
27
|
+
# The oldest Bundler with the after-eval hook, which an addressed vault needs.
|
|
28
|
+
# The plugin machinery these specs exercise is Bundler's own,
|
|
29
29
|
# so a stale version silently tests different code.
|
|
30
30
|
RUN gem install --no-document bundler -v 4.1.0
|
|
31
31
|
|
data/README.md
CHANGED
|
@@ -43,8 +43,11 @@ source "https://gemvault.invalid/vendor/private.gemv/" do
|
|
|
43
43
|
end
|
|
44
44
|
```
|
|
45
45
|
|
|
46
|
-
|
|
47
|
-
`type: :vault`, and
|
|
46
|
+
This form needs **Bundler 4.1.0 or newer**. On an older Bundler the plugin
|
|
47
|
+
still serves `type: :vault`, and an addressed vault fails as an unreachable
|
|
48
|
+
host. A plugin installed by an older Bundler has no redirect recorded, and
|
|
49
|
+
reinstalling over it does not add one: after moving to Bundler 4.1.0, delete
|
|
50
|
+
`.bundle/plugin` and install the plugin again.
|
|
48
51
|
|
|
49
52
|
`gemvault.invalid` resolves nowhere and is never contacted. Everything after it
|
|
50
53
|
is the vault's path relative to the Gemfile. The plugin publishes the vault as a
|
data/lib/gemvault/version.rb
CHANGED