@natjswenson/shipflow 0.3.1 → 0.3.2
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 +16 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,22 @@
|
|
|
2
2
|
|
|
3
3
|
All notable changes to `@natjswenson/shipflow` are documented here.
|
|
4
4
|
|
|
5
|
+
## 0.3.2 (2026-07-28) — actually render the README on npmjs.com
|
|
6
|
+
|
|
7
|
+
- **Fixed: the npm page still showed "No README data found" after 0.3.1.** That
|
|
8
|
+
release put README.md, LICENSE and CHANGELOG.md into the tarball (verified by
|
|
9
|
+
downloading it), which fixed what `npm install` delivers — but not the website.
|
|
10
|
+
npm reads README.md to populate the registry manifest's `readme` field when it
|
|
11
|
+
builds the publish manifest, which happens BEFORE the package's own `prepack`
|
|
12
|
+
hook runs. So the tarball had the file and the registry record did not.
|
|
13
|
+
Worse than merely empty: the stored value was the literal string
|
|
14
|
+
`ERROR: No README data found!`, and npmjs.com falls back to reading the
|
|
15
|
+
tarball only when that field is *absent* (compare `zod`, which renders fine
|
|
16
|
+
with no packument readme at all), so the error string kept winning.
|
|
17
|
+
The release workflow now stages the three files into the package directory
|
|
18
|
+
before `npm publish` is invoked at all, rather than relying on `prepack`.
|
|
19
|
+
Code unchanged.
|
|
20
|
+
|
|
5
21
|
## 0.3.1 (2026-07-28) — publish the README, LICENSE and CHANGELOG to npm
|
|
6
22
|
|
|
7
23
|
- **Fixed: the npm package shipped with no README, LICENSE or CHANGELOG.**
|
package/package.json
CHANGED