@xml-auditfile/auditfile 0.0.2-alpha.1 → 0.0.3
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 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -176,7 +176,7 @@ To use a local spec checkout instead: `SPEC_ROOT=../auditfile-spec npm test`.
|
|
|
176
176
|
| Workflow | What it does |
|
|
177
177
|
| -------- | ------------ |
|
|
178
178
|
| `ci.yml` | Push to main and pull requests: fetch the pinned spec, install, test on Node 20, 22 and 24, pack (dry run), audit dependencies |
|
|
179
|
-
| `release.yml` | Manual, with a version such as `1.0.1`. From `main` the version must be higher than every release; from `release/X.Y` (maintenance of an older line) it must be in line X.Y and higher than the latest release in that line. Then it fetches the pinned spec, tests, packs, creates the tag and GitHub release, and
|
|
179
|
+
| `release.yml` | Manual, with a version such as `1.0.1`. From `main` the version must be higher than every release; from `release/X.Y` (maintenance of an older line) it must be in line X.Y and higher than the latest release in that line. Then it fetches the pinned spec, tests, packs, creates the tag and GitHub release, and stages the version on npm through Trusted Publishing when the `NPM_PUBLISH` variable is `true` (environment `npm`). A staged version goes live only after a maintainer approves it with 2FA on npmjs.com (Staged Packages) or with `npm stage approve <stage-id>`. Dist-tags: `latest` for the highest stable release, `next` for a pre-release, `release-X.Y` for maintenance |
|
|
180
180
|
| `dependabot.yml` | Weekly updates of npm packages and GitHub Actions |
|
|
181
181
|
|
|
182
182
|
## License
|