@voxgig/create-sdkgen 0.29.0 → 0.29.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/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@voxgig/create-sdkgen",
|
|
3
|
-
"version": "0.29.
|
|
3
|
+
"version": "0.29.1",
|
|
4
4
|
"main": "dist/create-sdkgen.js",
|
|
5
5
|
"type": "commonjs",
|
|
6
6
|
"types": "dist/create-sdkgen.d.ts",
|
|
@@ -47,7 +47,8 @@
|
|
|
47
47
|
"dist",
|
|
48
48
|
"bin",
|
|
49
49
|
"project",
|
|
50
|
-
"LICENSE"
|
|
50
|
+
"LICENSE",
|
|
51
|
+
"README.md"
|
|
51
52
|
],
|
|
52
53
|
"devDependencies": {
|
|
53
54
|
"@types/node": "26.1.2",
|
|
@@ -62,7 +62,29 @@ The setup script configures GitHub Actions as the publishing source. It does
|
|
|
62
62
|
not commit, push, merge, or deploy. Push the documentation workflow and project
|
|
63
63
|
changes to its configured deployment branch to publish the website.
|
|
64
64
|
|
|
65
|
+
When a target publishes to npm, sdkgen generates `setup-npm-trust.sh` here.
|
|
66
|
+
For a repository on `github.com`, it registers each npm publish workflow as
|
|
67
|
+
the trusted publisher of its package, from the same model the workflows are
|
|
68
|
+
generated from, and leaves a package that is already set up alone:
|
|
69
|
+
|
|
70
|
+
```sh
|
|
71
|
+
.sdk/admin/setup-npm-trust.sh --dry-run
|
|
72
|
+
.sdk/admin/setup-npm-trust.sh
|
|
73
|
+
.sdk/admin/setup-npm-trust.sh --check
|
|
74
|
+
```
|
|
75
|
+
|
|
76
|
+
`--check` changes nothing and exits non-zero on any difference from what the
|
|
77
|
+
workflows need, including a trusted publisher that no workflow names;
|
|
78
|
+
`--replace` revokes those. It needs an npm login with publish rights. For a
|
|
79
|
+
repository hosted anywhere else, npm cannot trust GitHub Actions, so the script
|
|
80
|
+
says so and exits non-zero.
|
|
81
|
+
|
|
82
|
+
npm offers trusted publishing only for a package that already has a version,
|
|
83
|
+
so a new package's first version is published by hand, as `.sdk/PUBLISHING.md`
|
|
84
|
+
describes. Run the script straight after; every later release goes through the
|
|
85
|
+
generated workflow.
|
|
86
|
+
|
|
65
87
|
The status launcher and the drift check come from create-sdkgen; the status
|
|
66
|
-
reporting code
|
|
67
|
-
script. Put project-specific administration scripts
|
|
68
|
-
different names.
|
|
88
|
+
reporting code and the npm trust script come from sdkgen. Docgen owns the
|
|
89
|
+
generated Pages setup script. Put project-specific administration scripts
|
|
90
|
+
beside them with different names.
|