@aggc/or-info 0.2.17 → 0.2.18
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 +1 -27
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -352,33 +352,7 @@ Additional entry points:
|
|
|
352
352
|
|
|
353
353
|
## Release
|
|
354
354
|
|
|
355
|
-
|
|
356
|
-
The package is public under the `@aggc` npm scope.
|
|
357
|
-
|
|
358
|
-
Release checklist:
|
|
359
|
-
|
|
360
|
-
1. Update `CHANGELOG.md`.
|
|
361
|
-
2. Bump `version` in `package.json` **and** `manifest.json` (must match).
|
|
362
|
-
3. Run `npm test`.
|
|
363
|
-
4. Commit and push to `main`.
|
|
364
|
-
5. Create and push a matching tag:
|
|
365
|
-
|
|
366
|
-
```bash
|
|
367
|
-
git tag v0.x.0
|
|
368
|
-
git push origin v0.x.0
|
|
369
|
-
```
|
|
370
|
-
|
|
371
|
-
The publish workflow runs `npm ci`, `npm run test:local`, then
|
|
372
|
-
`npm publish --provenance --access public`.
|
|
373
|
-
|
|
374
|
-
Repository release requirements:
|
|
375
|
-
|
|
376
|
-
- GitHub secret `NPM_TOKEN` must exist for `jmtrs/or-info`.
|
|
377
|
-
- The token must have npm publish permission for `@aggc/or-info`.
|
|
378
|
-
- `id-token: write` is enabled so npm provenance is attached to published versions.
|
|
379
|
-
|
|
380
|
-
After the initial package bootstrap, prefer migrating to npm Trusted Publishing and then
|
|
381
|
-
remove `NPM_TOKEN` from the repository secrets.
|
|
355
|
+
See [CHANGELOG.md](CHANGELOG.md) for release history and details.
|
|
382
356
|
|
|
383
357
|
## Contributing
|
|
384
358
|
|