zeuslock-dlp-cli 0.2.0 → 0.2.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 +20 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -561,7 +561,26 @@ Rules export scopes:
|
|
|
561
561
|
|
|
562
562
|
This package is configured as `zeuslock-dlp-cli` and exposes the executable command `zeuslock`.
|
|
563
563
|
|
|
564
|
-
Before publishing, confirm that the npm account is the intended package owner, choose the final license, and verify that `package.json` is already at the intended release version.
|
|
564
|
+
Before publishing, confirm that the npm account is the intended package owner, choose the final license, and verify that `package.json` is already at the intended release version.
|
|
565
|
+
|
|
566
|
+
### GitHub Actions
|
|
567
|
+
|
|
568
|
+
Create a GitHub repository secret named `NPM_PUBLISH_TOKEN`. The token must belong to an npm account that can publish `zeuslock-dlp-cli`.
|
|
569
|
+
|
|
570
|
+
Release a new version:
|
|
571
|
+
|
|
572
|
+
```bash
|
|
573
|
+
npm version patch
|
|
574
|
+
git push origin main --follow-tags
|
|
575
|
+
```
|
|
576
|
+
|
|
577
|
+
The `vX.Y.Z` tag created by `npm version` triggers `.github/workflows/npm-publish.yml`. The workflow verifies the tag matches `package.json`, runs tests, checks publish contents, confirms the version is not already on npm, and publishes to the npm registry.
|
|
578
|
+
|
|
579
|
+
You can also run the workflow manually from the `main` branch in GitHub Actions. Manual runs publish the version already present in `package.json`.
|
|
580
|
+
|
|
581
|
+
### Manual Fallback
|
|
582
|
+
|
|
583
|
+
If you need to publish from a local machine, run:
|
|
565
584
|
|
|
566
585
|
```bash
|
|
567
586
|
npm publish --access public
|