Release Notes For Maintainers
WebTest AI beta releases are published from GitHub Actions.
Manual Beta Publish
Use the Publish Beta workflow.
Before a real publish, configure npm Trusted Publishing for the package:
- Publisher: GitHub Actions
- Organization or user:
asserthive - Repository:
webtest-ai - Workflow filename:
publish-beta.yml
- Bump
package.jsonandpackage-lock.jsonto the next unpublished prerelease version. - Run
npm run release:checklocally. - Run once with
dry_run=true. - Confirm the bounded V2 release gate, demo evidence pack,
npm pack --dry-run, and the npm version availability check pass. - Optionally run
npm run demo:intent -- --headedlocally to watch the intent evidence pack across the bundled whitelabel storefronts. - Run again with
dry_run=false. - Enter the exact confirmation string:
publish @asserthive/webtest-ai@0.1.0-beta.3
The workflow publishes through npm Trusted Publishing and GitHub Actions OIDC. It does not use the repository secret NPM_TOKEN. If the workflow reports that the version already exists on npm, bump to the next beta version before rerunning the publish job. If npm returns EOTP, the publish is still using token authentication; verify the trusted publisher settings above and rerun the workflow from .github/workflows/publish-beta.yml.
Local Package Rehearsal
Use this only when checking a release locally:
npm run release:check
npm test
npm run test:drivers:ci
npm run test:v2
npm run demo:v2
npm pack --dry-run
npm pack
mkdir -p /tmp/webtest-ai-smoke
cd /tmp/webtest-ai-smoke
npm install /path/to/asserthive-webtest-ai-0.1.0-beta.3.tgz
npx webtest-ai --help
npx webtest-ai --version
Beta Availability
WebTest AI is still in early beta. The public npm package is published under the beta tag while source access remains separate.
npm install --save-dev @asserthive/webtest-ai@beta