codeharbor 0.1.3 → 0.1.4
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 +13 -3
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -106,8 +106,13 @@ CodeHarbor supports auto publish to npm from GitHub Actions.
|
|
|
106
106
|
|
|
107
107
|
Setup once:
|
|
108
108
|
|
|
109
|
-
1.
|
|
110
|
-
|
|
109
|
+
1. Configure npm Trusted Publishing for this repository/workflow (preferred):
|
|
110
|
+
- npm package settings -> Trusted publishing -> Add publisher
|
|
111
|
+
- Provider: GitHub Actions
|
|
112
|
+
- Repository: `biglone/CodeHarbor`
|
|
113
|
+
- Workflow file: `.github/workflows/release-npm.yml`
|
|
114
|
+
2. Optional fallback: set repository secret `NPM_TOKEN` (npm automation token).
|
|
115
|
+
3. Push to `main` with a publish trigger commit message.
|
|
111
116
|
|
|
112
117
|
Trigger rules:
|
|
113
118
|
|
|
@@ -119,9 +124,14 @@ Trigger rules:
|
|
|
119
124
|
The workflow runs `typecheck`, `test`, `test:e2e` (Admin UI Playwright), `build`, `node dist/cli.js --help`, `npm pack --dry-run`, then publishes with:
|
|
120
125
|
|
|
121
126
|
```bash
|
|
122
|
-
npm publish --access public
|
|
127
|
+
npm publish --provenance --access public
|
|
123
128
|
```
|
|
124
129
|
|
|
130
|
+
Auth mode selection:
|
|
131
|
+
|
|
132
|
+
- If `NPM_TOKEN` secret exists: publish with token.
|
|
133
|
+
- If `NPM_TOKEN` is absent: publish via npm Trusted Publishing (OIDC).
|
|
134
|
+
|
|
125
135
|
If the same package version already exists on npm, publish is skipped automatically.
|
|
126
136
|
|
|
127
137
|
Release checklist (recommended):
|