Releasing doro-cli

This document outlines the process for releasing a new version of doro-cli.

Release Workflow

Prepare: Ensure you are on the latest main branch.
```
git checkout main
git pull origin main
```

Create Release Branch: Create a new branch for the release.

git checkout -b release/v1.0.0 # Replace with your version

Bump Version: Update the version in package.json.
```
npm version 1.0.0 --no-git-tag-version
```

Commit and Tag:

git add package.json
git commit -m "chore: release v1.0.0"
git tag -a v1.0.0 -m "Release v1.0.0"

Push: Push the branch and the tag to GitHub.

git push origin release/v1.0.0 --follow-tags

Merge to Main: Once the release CI passes, merge the release branch back into main.
```
git checkout main
git merge release/v1.0.0
git push origin main
```

The GitHub Actions workflow release.yml uses Trusted Publishing (OIDC):

Security: No NPM_TOKEN secret is required. GitHub authenticates directly with npm using OpenID Connect.
Provenance: The package is published with a verifiable link back to the GitHub Action that built it (--provenance).
Setup: Ensure you have added "GitHub Actions" as a Trusted Publisher in your npm package settings.

The workflow handles:

Tests & Linting: Runs the full verification suite.
GitHub Release: Creates a new release with automatically generated release notes.
NPM Publish: Automatically publishes to npm.

For release candidates (e.g., v1.0.0-rc.1), the flow is identical. The workflow is configured to mark these as "Prerelease" in GitHub.