@theokit/sdk 4.44.0 → 4.44.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.
- package/CHANGELOG.md +23 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,28 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 4.44.1
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- 0cabe27: `pnpm release` now verifies its tags reached the remote instead of trusting an exit code.
|
|
8
|
+
|
|
9
|
+
`changeset publish` creates one annotated tag per published package and pushes them, then reports
|
|
10
|
+
success on its own exit code — and an exit code is not evidence a ref transferred.
|
|
11
|
+
|
|
12
|
+
Measured 2026-08-11: `git push` contacts the remote BEFORE `pre-push` runs, `pre-push` runs the full
|
|
13
|
+
`pnpm validate` for around eleven minutes, and by the time the transfer begins the server has
|
|
14
|
+
dropped the idle connection. Git dies of SIGPIPE (exit 141) silently — no error text, nothing
|
|
15
|
+
transferred, output ending in `✓ pre-push gates passed`. A missing release tag is not noticed that
|
|
16
|
+
day; it is noticed weeks later by whoever is bisecting.
|
|
17
|
+
|
|
18
|
+
`scripts/verify-release-refs.mjs` compares the tags at a revision against `git ls-remote`, and is
|
|
19
|
+
wired into `pnpm release` after `changeset publish` rather than offered as a wrapper — a wrapper
|
|
20
|
+
only helps whoever remembers to call it.
|
|
21
|
+
|
|
22
|
+
Three distinct exit codes, because collapsing them is the failure being removed: `0` verified,
|
|
23
|
+
`1` a tag never reached the remote, `2` could not check (unreachable remote, or a revision that does
|
|
24
|
+
not resolve).
|
|
25
|
+
|
|
3
26
|
## 4.44.0
|
|
4
27
|
|
|
5
28
|
### Minor Changes
|
package/package.json
CHANGED