spyret 0.1.0 → 0.1.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/docs/RELEASING.md +7 -8
- package/package.json +1 -1
package/docs/RELEASING.md
CHANGED
|
@@ -12,12 +12,11 @@ merged release commit, run:
|
|
|
12
12
|
|
|
13
13
|
```sh
|
|
14
14
|
npm login
|
|
15
|
-
npm install --global npm@11.20.0
|
|
16
15
|
npm ci
|
|
17
16
|
npm run typecheck
|
|
18
17
|
npm test
|
|
19
|
-
npm run test:package -- --out release
|
|
20
|
-
npm publish ./release/spyret-0.1.0.tgz --access public
|
|
18
|
+
npx --yes --package npm@11.20.0 -c 'npm run test:package -- --out release'
|
|
19
|
+
npx --yes --package npm@11.20.0 npm publish ./release/spyret-0.1.0.tgz --access public
|
|
21
20
|
```
|
|
22
21
|
|
|
23
22
|
Also require green upstream PBT CI for this commit before publishing. The package
|
|
@@ -51,8 +50,8 @@ No npm token needs to be stored in GitHub. Publishing uses OIDC and provenance.
|
|
|
51
50
|
2. On the updated `main`, tag that exact commit and push the tag:
|
|
52
51
|
|
|
53
52
|
```sh
|
|
54
|
-
git tag v0.1.
|
|
55
|
-
git push origin v0.1.
|
|
53
|
+
git tag v0.1.2
|
|
54
|
+
git push origin v0.1.2
|
|
56
55
|
```
|
|
57
56
|
|
|
58
57
|
3. `release.yml` verifies the tag matches `package.json` and belongs to `main`,
|
|
@@ -64,6 +63,6 @@ workflow can be rerun or manually dispatched against the same **tag**. An existi
|
|
|
64
63
|
npm version is accepted only when its integrity matches the tested tarball;
|
|
65
64
|
different contents require a version bump.
|
|
66
65
|
|
|
67
|
-
|
|
68
|
-
|
|
69
|
-
|
|
66
|
+
Version 0.1.0 was bootstrapped manually. Subsequent versions use the tagged
|
|
67
|
+
workflow. It installs its pinned npm into a separate tools directory so npm
|
|
68
|
+
does not replace itself while running.
|