@scrymore/scry-sbcov 0.4.0 → 0.4.1-next.20260910192038
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 +23 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -24,6 +24,29 @@ Or run directly with npx:
|
|
|
24
24
|
npx @scrymore/scry-sbcov
|
|
25
25
|
```
|
|
26
26
|
|
|
27
|
+
### Snapshot channels
|
|
28
|
+
|
|
29
|
+
Pushes to `stage` publish `@scrymore/scry-sbcov@next`. The daily schedule
|
|
30
|
+
publishes `@nightly` from `main`; manual runs select the channel from the chosen
|
|
31
|
+
branch (`stage` → `next`, `main` → `nightly`). Other branches cannot publish.
|
|
32
|
+
Stable releases from `main` still use the existing Changesets release PR and
|
|
33
|
+
`latest` channel.
|
|
34
|
+
|
|
35
|
+
```bash
|
|
36
|
+
npm install --save-dev @scrymore/scry-sbcov@next
|
|
37
|
+
```
|
|
38
|
+
|
|
39
|
+
The channel moves with each snapshot; pin the resolved prerelease version for a
|
|
40
|
+
reproducible build. Snapshots use a temporary patch changeset even when no release
|
|
41
|
+
changesets remain, and never commit generated versions or create Git tags. Runs
|
|
42
|
+
are serialized per branch and verify the prerelease suffix before publishing.
|
|
43
|
+
|
|
44
|
+
After merging this CI change, create `stage` from `main`. Both channels use the
|
|
45
|
+
existing repository `NPM_TOKEN` secret via setup-node's `NODE_AUTH_TOKEN`; it must
|
|
46
|
+
have npm publish permission for this package. No additional secret is required.
|
|
47
|
+
If GitHub has disabled the scheduled workflow for inactivity, re-enable
|
|
48
|
+
**Snapshot Release** in Actions. No npm dist-tag needs to be created manually.
|
|
49
|
+
|
|
27
50
|
## Quick Start
|
|
28
51
|
|
|
29
52
|
```bash
|