vite-plugin-ai-auto-i18n 0.9.0 → 0.9.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 +6 -2
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -569,8 +569,12 @@ Every push to `main` runs [.github/workflows/release.yml](.github/workflows/rele
|
|
|
569
569
|
Test coverage in the release pipeline:
|
|
570
570
|
|
|
571
571
|
- The `verify` job runs `npm run test:coverage`, which runs the suite with V8 coverage on `src/**` and writes `coverage/coverage-summary.json`. That summary is uploaded as the `coverage-summary` artifact.
|
|
572
|
-
- The
|
|
573
|
-
-
|
|
572
|
+
- The `verify` job also runs `npm pack --dry-run --json` after the build and uploads the report as the `package-pack` artifact.
|
|
573
|
+
- The GitHub Release notes end with three generated sections:
|
|
574
|
+
- `## Test coverage`, from the coverage summary, with statements, branches, functions, and lines for the commit being released.
|
|
575
|
+
- `## Package`, with tarball size, unpacked size, and file count, plus distribution by location and by type.
|
|
576
|
+
- `## Dependencies`, with runtime and peer dependencies from `package.json`. Dependencies are not bundled into `dist/`.
|
|
577
|
+
- No coverage threshold is enforced and no size limit is checked. A drop in coverage or an increase in package size does not block a release.
|
|
574
578
|
- To check coverage before pushing to `main`, run the command in [Test coverage](#-test-coverage) locally.
|
|
575
579
|
|
|
576
580
|
## 🧪 Test coverage
|