docs: clarify CLI version check

[bgardiner]

Pull Request Submission Checklist

• Follows CONTRIBUTING guidelines
• Commit messages are release-note ready, emphasizing what was changed, not how.
• Includes detailed description of changes
• Contains risk assessment (Low | Medium | High)
• Highlights breaking API changes (if applicable)
• Links to automated tests covering new functionality
• Includes manual testing instructions (if necessary)
• Updates relevant GitBook documentation (PR link: N/A - README-only CI trigger change)
• Includes product update to be announced in the next stable release notes

What does this PR do?

Adds a short note to the README showing snyk --version as a way to confirm which CLI release is installed. This is a documentation-only change intended to trigger CI on a pull request.

Risk assessment: Low.

Where should the reviewer start?

README.md

How should this be manually tested?

No manual testing is required for this documentation-only change.

Validation performed:

• npx prettier --check README.md
• BUILD_MODE=public make lint (TypeScript linting, formatting checks, and Go linting completed; final tidy verification failed because this cloud environment cannot access the private github.com/snyk/remy-cli-extension module.)

What's the product update that needs to be communicated to CLI users?

None.

  

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.