nexusinno-renovate-setup-cli
v1.2.0
Published
Outil CLI pour facilement mettre en place et intégrer Renovate dans les projets
Maintainers
Readme
nexusinno-renovate-setup-cli
CLI tool to set up self-hosted Renovate in Azure DevOps projects.
Installation
npm install -g nexusinno-renovate-setup-cliUsage
Navigate to your project root and run:
renovate-setupThe CLI guides you through interactive setup:
- Azure DevOps endpoint (auto-detected from git remote)
- Repository name (auto-detected from git remote)
- Base branch (optional, for targeting PRs)
- Stack configuration (backend, frontend, mobile, etc.)
- Stack paths (for monorepo support)
- Version constraints (optional, lock packages to specific versions)
Generated Files
renovate.json (project root)
- Stack-based PR grouping (patches/minors weekly, majors monthly)
- Version constraints for locked packages
- Schedule configuration (Monday 12am-6am)
- Only scans configured stack paths
.renovate/renovate-pipeline.yml
- Scheduled runs (Monday 4:00 AM)
- Manual run with "Ignore schedule restrictions" parameter
- Environment variables for tokens and base branch
- Node.js 22.x runtime
.renovate/README.md
- Token creation instructions (Azure DevOps + GitHub)
- Pipeline setup guide
- Schedule behavior explanation
- Customization options
Features
- 🎯 Multi-stack support with path configuration
- 📦 Version constraints (e.g.,
<15.0.0) - 📅 Smart scheduling (weekly patches/minors, monthly majors)
- ⚡ Self-hosted via Azure Pipeline
- 🎛️ Schedule override for manual testing
- 🏢 Monorepo ready
Next Steps
After generation:
- Create Azure DevOps PAT (Code: Read & Write, PR Threads: Read & Write)
- Create GitHub PAT (public_repo scope for release notes)
- Set up Azure Pipeline from
.renovate/renovate-pipeline.yml - Add secret variables:
RENOVATE_TOKENandGITHUB_COM_TOKEN - Test with "Ignore schedule restrictions" parameter
See generated .renovate/README.md for detailed instructions.
License
ISC
Author
Nexus Innovations (Antoine Bouabana)
