@yeti-cgi/debugging-fun 0.1.0 → 0.1.1-alpha.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/README.md +11 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -55,7 +55,17 @@ The included GitHub Actions workflow publishes whenever a GitHub Release is publ
|
|
|
55
55
|
4. In GitHub, create an environment named `npm`. Add required reviewers if desired.
|
|
56
56
|
5. Update `package.json` to a version not already published, commit it, tag it (for example `v0.1.0`), and publish the matching GitHub Release.
|
|
57
57
|
|
|
58
|
-
No long-lived `NPM_TOKEN` secret is required. The workflow requests an OIDC identity token
|
|
58
|
+
No long-lived `NPM_TOKEN` secret is required. The workflow requests an OIDC identity token; provenance is currently disabled by `publishConfig.provenance`.
|
|
59
|
+
|
|
60
|
+
### Alpha releases
|
|
61
|
+
|
|
62
|
+
Every push to the `staging` branch publishes a unique prerelease such as `0.1.1-alpha.42` under npm's `alpha` dist-tag. Install the newest staging build with:
|
|
63
|
+
|
|
64
|
+
```sh
|
|
65
|
+
npm install @yeti-cgi/debugging-fun@alpha
|
|
66
|
+
```
|
|
67
|
+
|
|
68
|
+
Alpha publishing does not change the stable `latest` tag. Keep `package.json` set to the intended next stable version; publishing a GitHub Release publishes that exact version under `latest`.
|
|
59
69
|
|
|
60
70
|
## Development
|
|
61
71
|
|
package/package.json
CHANGED