eco-helpers 3.2.17 → 3.2.18
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 +28 -0
- data/lib/eco/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: 9238296c1185b73d2dfa18af81387f01e7b913af4fa3732491dfeed4a7ba6caf
|
|
4
|
+
data.tar.gz: 4b8a882badc3d22c2ba166e45284e1b4d1e3912afa8a2452072765917165fe3b
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 1b0abd929fdb1827a544d18ec6c2a2a49b0807caedae00603f6d656c8e8f4498b5ea500f8f3845fcd44187f156125916456326513da21134c16a73ba7eee32ee
|
|
7
|
+
data.tar.gz: 755a6f6efa59752b4897506be1bdc2b408a2e7f84c26330b7c192dd805ff3851b13966e8516da6e61517d86b3cb267a6e8884a26069ea20f8be962d5e1886f18
|
data/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,34 @@
|
|
|
2
2
|
|
|
3
3
|
All notable changes to this project will be documented in this file.
|
|
4
4
|
|
|
5
|
+
## [3.2.18] - 2026-07-10
|
|
6
|
+
|
|
7
|
+
Version-identity + regression-guard release. **No behaviour change** vs the fixed `3.2.17` build —
|
|
8
|
+
this bump exists so the LocationDraft fix can be pinned/verified by version, and adds an offline
|
|
9
|
+
guard so the dead-fragment class of bug can't reach production again.
|
|
10
|
+
|
|
11
|
+
### Why this bump
|
|
12
|
+
|
|
13
|
+
`3.2.17` shipped as **two different builds under one version**: the version was bumped to `3.2.17`
|
|
14
|
+
on 2026-07-04 (`243822b9`), then the live-crash fix `352a9657` (LocationDraft dead-fragment
|
|
15
|
+
convention) landed on 2026-07-05 — keeping the same `3.2.17` label. Because `3.2.17` is installed
|
|
16
|
+
from git/path (unpublished), a consumer bundled in that ~26h window reports `3.2.17` yet lacks the
|
|
17
|
+
fix. This crashed the **live act-gov** org-structure sync again on 2026-07-09 with the exact
|
|
18
|
+
`uninitialized constant …Fragment::LocationDraft (NameError)`. Bumping to `3.2.18` makes the fixed
|
|
19
|
+
build unambiguously identifiable: any consumer on `>= 3.2.18` provably has the fix.
|
|
20
|
+
|
|
21
|
+
### Added
|
|
22
|
+
|
|
23
|
+
- **Regression-guard spec for the dead-fragment convention.**
|
|
24
|
+
`spec/…/helpers/location/command/end_points/optimizations_spec.rb` scans every file under
|
|
25
|
+
`usecases/graphql/` and fails if any references a fragment via the removed `___Const__Fragment` /
|
|
26
|
+
`::Fragment::<Name>` constant convention (the exact NameError that crashed act-gov), and asserts
|
|
27
|
+
the three Location command payload procs still route fragments through the `spread :Name` registry
|
|
28
|
+
DSL. It is a SOURCE lint, not a full offline render: rendering needs the graphlient fork's
|
|
29
|
+
`to_query_string`/`spread` DSL, but eco-helpers' own bundle resolves stock graphlient `0.8.0` (the
|
|
30
|
+
fork is pinned only in the deployment/gem bundles). If eco-helpers later pins the fork in dev/test,
|
|
31
|
+
promote this to a real render guard like the gem's `tests/validate_queries.rb`.
|
|
32
|
+
|
|
5
33
|
## [3.2.17] - 2026-07-04
|
|
6
34
|
|
|
7
35
|
Native GraphQL template build+maintenance + ooze-native migration (strangler-fig): pure,
|
data/lib/eco/version.rb
CHANGED