elseware-docs-engine 1.3.1 → 1.3.2
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 +18 -0
- package/dist/index.css +1 -1
- package/dist/index.css.map +1 -1
- package/package.json +6 -3
package/README.md
CHANGED
|
@@ -138,6 +138,24 @@ export default docs;
|
|
|
138
138
|
|
|
139
139
|
## Development
|
|
140
140
|
|
|
141
|
+
Pull requests targeting `main` run the complete validation suite and verify
|
|
142
|
+
that the package version has not already been published. A successful merge to
|
|
143
|
+
`main` runs the same checks and publishes through GitHub's OIDC trusted
|
|
144
|
+
publishing; no long-lived npm token is stored in GitHub. Because this source
|
|
145
|
+
repository is private, npm provenance is disabled.
|
|
146
|
+
|
|
147
|
+
Configure npm Trusted Publishing for `elseware-docs-engine` using repository
|
|
148
|
+
`elsewaretechnology/elseware-docs-engine`, workflow `publish.yml`, and the
|
|
149
|
+
GitHub environment `npm-production`. Keep `package.json` and
|
|
150
|
+
`package-lock.json` synchronized and bump the version in the release PR:
|
|
151
|
+
|
|
152
|
+
```bash
|
|
153
|
+
npm version patch --no-git-tag-version
|
|
154
|
+
```
|
|
155
|
+
|
|
156
|
+
The workflow fails when the exact version already exists on npm. If the
|
|
157
|
+
repository becomes public, remove `--provenance=false` to enable provenance.
|
|
158
|
+
|
|
141
159
|
```bash
|
|
142
160
|
npm install
|
|
143
161
|
npm run dev
|