Harness

Publishing

Harness is published to npm as @antubattle/harness and exposes the harness executable through its bin mapping.

Prerequisites

1. Log in to npm with an account that owns the @antubattle scope.
2. Ensure the working tree is clean.
3. Get explicit approval for the release bookkeeping if it has not already been requested.
4. Update CHANGELOG.md for the release.
5. Bump the version in package.json before each new release.

Authenticate

npm login
npm whoami

npm whoami should print antubattle before you publish.

If the npm account enforces publish-time 2FA, npm publish will require a current OTP or a granular access token that is allowed to bypass 2FA for publishing.

Build

npm run build

Test

npm test

Verify The Packed Artifact

npm run smoke:pack
npm pack --dry-run

The smoke test installs the tarball into a temporary directory and runs the packaged harness binary. The dry run shows exactly what would be published.

Publish

npm publish

package.json sets publishConfig.access to public, so the scoped package is published publicly.

If npm prompts for a one-time password, rerun the publish with:

npm publish --otp <code>

Verify The Published Package

npm view @antubattle/harness name version description --json

Users can then install the CLI with:

npm install -g @antubattle/harness

Publish Checklist

1. Ensure the working tree is clean.
2. Confirm the npm account owns the @antubattle scope.
3. Confirm CHANGELOG.md is updated for the release.
4. Bump the package version for the release.
5. Run the build and test commands.
6. Run the packaging smoke test.
7. Inspect npm pack --dry-run.
8. Run npm publish.
9. Verify the published metadata with npm view @antubattle/harness.

GitHub-Hosted Docs

These pages live under docs/ and are written to be compatible with a GitHub-hosted documentation flow based on that directory.

This site is open source. Improve this page.