goravel-vite-plugin 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/README.md +9 -2
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -182,8 +182,15 @@ The tests run a real Vite build and dev server in a temporary directory. Node st
|
|
|
182
182
|
### Releasing
|
|
183
183
|
|
|
184
184
|
1. Bump `version` in `package.json` and move the `Unreleased` entries in [CHANGELOG.md](CHANGELOG.md) under the new version.
|
|
185
|
-
2. Commit, tag `vX.Y.Z` and push the tag.
|
|
186
|
-
3.
|
|
185
|
+
2. Commit, tag `vX.Y.Z` and push the tag. The [`publish`](.github/workflows/publish.yml) workflow builds, tests and stages the release with `npm stage publish`; a hyphenated version (`v0.2.0-beta.1`) stages to the `next` dist-tag instead of `latest`.
|
|
186
|
+
3. Approve the staged release with 2FA. The job summary carries the command:
|
|
187
|
+
```bash
|
|
188
|
+
npm stage approve <stage-id>
|
|
189
|
+
```
|
|
190
|
+
You can also approve on npmjs.com under *Staged Packages*. Nothing is installable before that. A version can be staged only once — to rebuild, `npm stage reject <stage-id>`, fix, and push the tag again.
|
|
191
|
+
4. To rehearse, run the workflow by hand and leave *dry run* on: it needs no credentials and stages nothing.
|
|
192
|
+
|
|
193
|
+
Staging uses npm [trusted publishing](https://docs.npmjs.com/trusted-publishers) and [staged publishing](https://docs.npmjs.com/staged-publishing), so no npm token is stored here. The trusted publisher on npmjs.com is organization `goravel`, repository `vite-plugin`, workflow `publish.yml`, no environment, and it is stage-only: it allows `npm stage publish`, while `npm publish` and `npm dist-tag` are deliberately left disallowed — that is npm's maximum-security posture, and a dist-tag grant could repoint `latest` without any staged approval. `0.1.0` went out by hand before the workflow existed.
|
|
187
194
|
|
|
188
195
|
## Contributing
|
|
189
196
|
|