Release Process

1. Version Bump Follow semantic versioning for every package in the monorepo:

   pnpm version patch          # updates root package.json
   pnpm -r exec "pnpm version patch"   # or run per package (cli, core, test-utils, examples)
   

   
   Commit the changes alongside changelog/docs updates.
2. Build, Lint & Test (non-interactive)

   pnpm lint
   pnpm -w test:ci
   

   
   test:ci runs pnpm run build && vitest run --reporter=dot, ensuring no interactive prompts stall the release.
3. Docs sanity check

   pnpm -r --filter ./docs/oplink-docs dev   # optional local preview
   

   
   Verify Advanced sections (mcporter + authentication) and README references.
4. Publish Publish to npm:

   npm publish
   

   
   For alpha or beta releases:

   npm publish --tag alpha
   

5. Tag & Release Notes
   • Push git tags to GitHub
   • Draft release notes detailing changes

After publishing, confirm that npx oplink@latest pulls the correct version. Thank you for helping ensure OPLINK remains robust and up-to-date.