pgserve 2.6.8 → 2.6.9
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.
- package/CHANGELOG.md +43 -0
- package/package.json +1 -1
- package/scripts/assemble-tarball.sh +6 -1
package/CHANGELOG.md
CHANGED
|
@@ -14,6 +14,49 @@ All notable changes to `pgserve` are documented here. The format follows
|
|
|
14
14
|
[Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and this project adheres
|
|
15
15
|
to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
|
16
16
|
|
|
17
|
+
## [2.6.9] - 2026-05-12
|
|
18
|
+
|
|
19
|
+
**The actual final v2.x publish.** Bundles every fix needed to get
|
|
20
|
+
Build Tarballs → Sign + Attest → release-publish completing end-to-end
|
|
21
|
+
on the two platforms the v2.x signed-tarball pipeline supports.
|
|
22
|
+
|
|
23
|
+
### Fixed
|
|
24
|
+
|
|
25
|
+
- `scripts/assemble-tarball.sh` — defensive `${tar_flags[@]+...}`
|
|
26
|
+
expansion. macOS BSD tar lacks `--sort`/`--mtime`/`--owner`, so the
|
|
27
|
+
array stays empty on darwin runners; under `set -u`, expanding an
|
|
28
|
+
empty array errored as `tar_flags[@]: unbound variable` and broke
|
|
29
|
+
every darwin-* build.
|
|
30
|
+
|
|
31
|
+
### Changed (matrix scope)
|
|
32
|
+
|
|
33
|
+
Per Felipe directive 2026-05-12 ("just windows macos and linux, no
|
|
34
|
+
Intel Mac"), the signed-tarball pipeline matrix is reduced to the
|
|
35
|
+
platforms that actually have a working @embedded-postgres npm
|
|
36
|
+
package + a wired-in build path:
|
|
37
|
+
|
|
38
|
+
- ✅ `linux-x64-glibc` (linux)
|
|
39
|
+
- ✅ `darwin-arm64` (macos — Apple Silicon)
|
|
40
|
+
- ❌ `darwin-x64` — dropped (Intel Mac)
|
|
41
|
+
- ❌ `linux-arm64` — never working (no upstream pkg)
|
|
42
|
+
- ❌ `linux-x64-musl` — never working (no upstream pkg)
|
|
43
|
+
- 🔁 `windows-x64` — continues to ship via npm (version.yml inline
|
|
44
|
+
publish); not in the signed-tarball pipeline
|
|
45
|
+
|
|
46
|
+
### Consumer impact
|
|
47
|
+
|
|
48
|
+
- `@withone/cli` and any other npm dependent: zero impact — npm package
|
|
49
|
+
installs the same way, optional native deps still cover windows-x64
|
|
50
|
+
+ darwin-x64 + linux-x64 + darwin-arm64 via @embedded-postgres.
|
|
51
|
+
- Operators expecting GH Release signed tarballs: linux-x64 + darwin-
|
|
52
|
+
arm64 only. v2.x is end-of-line for Intel Mac signed tarballs.
|
|
53
|
+
|
|
54
|
+
### Cohort wrap-up
|
|
55
|
+
|
|
56
|
+
This is **the** last `pgserve`-named npm publish. Subsequent
|
|
57
|
+
development moves to the `autopg` package starting at v3.0.0 from the
|
|
58
|
+
new `automagik-dev/autopg` repo (post org transfer).
|
|
59
|
+
|
|
17
60
|
## [2.6.8] - 2026-05-12
|
|
18
61
|
|
|
19
62
|
**Final v2.x maintenance release with full signed-tarball GH Release.**
|
package/package.json
CHANGED
|
@@ -165,7 +165,12 @@ assemble_one() {
|
|
|
165
165
|
tar_flags+=(--owner=0 --group=0 --numeric-owner)
|
|
166
166
|
fi
|
|
167
167
|
|
|
168
|
-
|
|
168
|
+
# macOS BSD tar lacks --sort/--mtime/--owner, so tar_flags can stay
|
|
169
|
+
# empty on darwin-* runners. Under `set -u` (script-wide), expanding
|
|
170
|
+
# "${tar_flags[@]}" on an empty array errors as `tar_flags[@]: unbound
|
|
171
|
+
# variable`. The `${arr[@]+"${arr[@]}"}` pattern expands the array
|
|
172
|
+
# only when it has elements, leaving the command intact otherwise.
|
|
173
|
+
tar -C "$stage" -czf "$tarball" ${tar_flags[@]+"${tar_flags[@]}"} autopg/ || return 1
|
|
169
174
|
echo " ✓ tarball: $tarball ($(du -h "$tarball" | cut -f1))"
|
|
170
175
|
|
|
171
176
|
# 4) outer SHA256 — Group 8 cosign-signs this; Group 9 publishes both.
|