chore: point repository references at the VeraTools org - #46
Conversation
Leave the LICENSE copyright holder attribution unchanged. No historical narrative mentions were present.
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
Pull request overview
Updates hardcoded repository and container image references from lemon07r/Vera to the canonical VeraTools/Vera after the repository move, so installers, upgrade checks, and documentation point at the correct org.
Changes:
- Updated release-check / upgrade polling to query
VeraTools/Vera. - Updated npm + Python wrapper defaults and package metadata URLs to
VeraTools/Vera. - Updated docs/README links and Docker image references to
ghcr.io/veratools/vera.
Reviewed changes
Copilot reviewed 10 out of 11 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
| README.md | Updates badges and skills CLI snippet to the new org/repo. |
| crates/vera-cli/src/update_check.rs | Points the GitHub release check at VeraTools/Vera. |
| packages/npm-cli/bin/vera.js | Changes npm wrapper default release repo to VeraTools/Vera. |
| packages/npm-cli/package.json | Updates homepage/repo/issues metadata URLs to the new org. |
| packages/npm-cli/README.md | Updates documentation links to the new org/repo. |
| packages/python-cli/src/vera_ai_wrapper/main.py | Changes Python wrapper default release repo to VeraTools/Vera. |
| packages/python-cli/pyproject.toml | Updates author and project URLs to VeraTools. |
| packages/python-cli/README.md | Updates documentation links to the new org/repo. |
| docs/installation.md | Updates releases/source clone/Docker image references to the new org/image. |
| docs/docker.md | Updates GHCR image references and example configs to ghcr.io/veratools/vera. |
| CONTRIBUTING.md | Updates clone URL to the new org/repo. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| | Install agent skills | `vera agent install` | | ||
|
|
||
| For the full backend matrix, model options, Docker setup, and troubleshooting, see the main [README](https://github.com/lemon07r/Vera) and [Installation Guide](https://github.com/lemon07r/Vera/blob/master/docs/installation.md). | ||
| For the full backend matrix, model options, Docker setup, and troubleshooting, see the main [README](https://github.com/VeraTools/Vera) and [Installation Guide](https://github.com/VeraTools/Vera/blob/master/docs/installation.md). |
| | Install agent skills | `vera-ai agent install` | | ||
|
|
||
| For the full backend matrix, model options, Docker setup, and troubleshooting, see the main [README](https://github.com/lemon07r/Vera) and [Installation Guide](https://github.com/lemon07r/Vera/blob/master/docs/installation.md). | ||
| For the full backend matrix, model options, Docker setup, and troubleshooting, see the main [README](https://github.com/VeraTools/Vera) and [Installation Guide](https://github.com/VeraTools/Vera/blob/master/docs/installation.md). |
| # Vera | ||
|
|
||
| [](https://github.com/lemon07r/Vera/blob/master/LICENSE) | ||
| [](https://github.com/VeraTools/Vera/blob/master/LICENSE) |
|
@cubic-dev-ai review |
@lemon07r I have started the AI code review. It will take a few minutes to complete. |
|
@coderabbitai review |
|
|
Warning Review limit reached
Next review available in: 59 minutes Limit details: You’ve used all 3 included reviews currently available. Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits within each organization. For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (11)
Comment |
The repo moved from lemon07r/Vera to VeraTools/Vera. GitHub redirects keep old links working, but this updates all hardcoded references to the canonical org.
crates/vera-cli/src/update_check.rs: release-check API now queries VeraTools/Vera (whatvera upgradepolls)packages/npm-cli/bin/vera.js,packages/python-cli/src/vera_ai_wrapper/__main__.py: release-download repo defaultpackages/npm-cli/package.json,packages/python-cli/pyproject.toml: homepage/repository/issues URLs (and pyproject author now VeraTools; LICENSE copyright attribution intentionally unchanged)rg lemon07rafter this change matches only the LICENSE copyright line. cargo fmt clean; no test asserts the old URL.Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.Summary by cubic
Point all hardcoded references from
lemon07r/VeratoVeraTools/Veraso upgrade checks, installers, and docs use the canonical repo and GHCR image. Old GitHub links continue to work via redirects.vera upgradeandvera-ai upgradenow queryVeraTools/Vera; release downloads default to that repo inpackages/npm-cliandpackages/python-cli.ghcr.io/veratools/veraimages; update any local configs usingghcr.io/lemon07r/vera.homepage,repository,issues; Python author) now point toVeraTools. LICENSE attribution unchanged.lemon07r; no code relies on the old path.Written for commit f83bad2. Summary will update on new commits.