Felipe Santos
18c9c9340e
* fix(gerrit): remove memCache to fix prNo coming as null when pr-created * perf(gerrit): remove custom scm functions * Fully remove login parameter from configureScm() * Fetch refspecs in batches * Remove unnecessary error handling * Add tests * Throw if branch init fails * Simplify tests a little * Reduce more the tests * More test changes * Reuse the existing test setup more * Undo test import change * Improve initializeBranchesFromRefspecs JSDoc * The same for deleteBranchCreatedFromRefspec * Reduce a log to trace level * Abandon Code-Review -2 changes before initializing repository * Simply initialize the branches after git.initRepo() * Rework approach to be more generic * Add TODO comment about commitAndPush() * fix(gerrit): defer change creation to `createPr()` Signed-off-by: Felipe Santos <felipe.santos@ericsson.com> * Refactor hashtags handling * Add prTitle to all missing commitAndPush() * Fix type check * Fix test issue * Fix gerrit tests * Add warning when prTitle is set in updatePr * Remove now useless labels from commitAndPush * Fix gerrit client coverage * Fix gerrit scm coverage * Fix rebase coverage * Improve TODO about assignees * Fix formatting * Fix review comment * Extract to a pushForReview function * Fix after #41382 * Fix onboarding * Cleanup code * Fix ESLint * Fix tests * Restore gitRetry for git.merge * Fix tests * Simplify hashtags code * Delete pendingChangeBranch in pushForReview() * Fix test name * Remove unnecessary test comments * Improve test name again * Fix another test name * Delete local branch in Gerrit SCM * Add test for deleting pending branch * Add tests for pushForReview() * Simplify/optimize commitAndPush * Align jsdoc terminology on virtual branches * Remove no longer relevant TODO * Update virtal branch on push * Simplify deleteVirtualBranch * Fix test case name * Improve another test name * Restore test deleted by mistake * Fix another small test inconsistency * Fix coverage * Fix Renovate not detecting modified commits * Simplify Gerrit commitAndPush by leveraging git.commitFiles * Fix some code style issues * Revert "Simplify Gerrit commitAndPush by leveraging git.commitFiles" This reverts commitd71edcc279. * Fix another small code style issue * Use isUndefined instead * Fix one small test style issue * Fix more code style issues * Fix Gerrit mergeToLocal trying to fetch (and probably failing) * Extract refs/remotes/origin to a function * Rename virtualBranchRef to remoteBranchRef * Fix remoteBranchRef tsc * Consistently use currentRevision in Gerrit tests * Remove unnecessary type assertion * Instrument "fetch virtual branches" * Remove pendingChangeBranches, avoid overriding deleteBranch and mergeToLocal * Optimize virtual branches fetch (no longer requires update-ref), convert virtualBranches to Record, rename setVirtualBranch to registerVirtualBranch * Combine registerVirtualBranch and updateVirtualBranch into a single setVirtualBranch, and update ref in virtual branch too * Fix virtualBranches not being initialized * Add some debug logs * Simplify mergeToLocal for virtual branches * Revert "Simplify mergeToLocal for virtual branches" This reverts commit375d57a474. * Remove useless isVirtual const * test(git): add toThrow message for virtualBranches fetch error Satisfy vitest/require-to-throw-message so oxlint passes. * Update lib/util/git/types.ts Co-authored-by: RahulGautamSingh <rahultesnik@gmail.com> * Address review feedback --------- Signed-off-by: Felipe Santos <felipe.santos@ericsson.com> Co-authored-by: RahulGautamSingh <rahultesnik@gmail.com>
What is the Mend Renovate CLI?
Renovate is an automated dependency update tool. It helps to update dependencies in your code without needing to do it manually. When Renovate runs on your repo, it looks for references to dependencies (both public and private) and, if there are newer versions available, Renovate can create pull requests to update your versions automatically.
Features
- Delivers update PRs directly to your repo
- Relevant package files are discovered automatically
- Pull Requests automatically generated in your repo
- Provides useful information to help you decide which updates to accept (age, adoption, pass rates, merge confidence)
- Highly configurable and flexible to fit in with your needs and repository standards
- Largest collection of languages and platforms (listed below)
- Connects with private repositories and package registries
Languages
Renovate can provide updates for most popular languages, platforms, and registries including: npm, Java, Python, .NET, Scala, Ruby, Go, Docker and more. Supports over 90 different package managers.
Platforms
Renovate updates code repositories on the following platforms: GitHub, GitLab, Bitbucket, Azure DevOps, AWS Code Commit (experimental), Gitea, Forgejo, Gerrit (experimental), SCM-Manager (experimental)
Ways to run Renovate
The most effective way to run Renovate is to use an automated job scheduling system that regularly runs Renovate on all enabled repositories and responds with priority to user activity. Mend offers cloud-hosted and self-hosted solutions. See the options below.
Mend Renovate Community (Cloud-Hosted)
Supports: GitHub.com, Bitbucket Cloud
Hosted by Mend.io. No setup is needed. Community plan available (Free)
- GitHub Cloud: Install the Renovate Cloud-Hosted App on your GitHub org, then select the repos to enable
- Bitbucket Cloud: Add the Mend App to your Workspace, then add the Mend Renovate user to the projects you want to enable
Mend Renovate Community (Self-hosted)
Supports: GitHub, GitLab, Bitbucket Data Center
Install and run your own Renovate server. Access internal packages.
- Mend Renovate Community Self-Hosted (Free)
- Mend Renovate Enterprise (Paid plan)
Other ways to run Renovate
If you can’t use a pre-built job scheduling system, or want to build your own, the following options are available:
Run Renovate on your Pipeline
Mend provides a GitHub Action or a GitLab Runner to help you run Renovate as a CI pipeline job.
- GitHub Action: renovatebot/github-action.
- GitLab Runner: Renovate Runner project
- AzureDevOps action: Renovate Me extension
Note: This extension is created and maintained personally by a Renovate developer/user. Support requests for the extension will not be answered directly in the main Renovate repository. - Custom pipeline: You can create a custom pipeline with a yml definition that triggers npx renovate. More details on how to configure the pipeline.
Run Renovate CLI
There are several ways to run the Renovate CLI directly. See docs: Running Renovate for all options.
Supports: all platforms
For additional community-maintained options, see the Community Tools page.
Docs
More about Renovate
- Renovate basics
- Supported platforms and languages
- Advanced Renovate usage
Renovate Docs
Comparisons
Get involved
Issues and Discussions
Please open a Discussion to get help, suggest a new feature, or to report a bug. We only want maintainers to open Issues.
Contributing
To contribute to Renovate, or run a local copy, please read the contributing guidelines.
- Guidelines for Contributing
- Items that need contribution: good first issues
Contact and Social Media
The Renovate project is proudly supported and actively maintained by Mend.io.
- Contact Mend.io for commercial support questions.
Follow us on:
- Twitter: x.com/mend_io
- LinkedIn: linkedin.com/company/mend-io
Security / Disclosure
If you find any bug with Renovate that may be a security problem, please report it through the GitHub Security Advisories process. This way we can evaluate the bug and hopefully fix it before it gets abused. Please give us enough time to investigate the bug before you report it anywhere else.
If you would like to discuss a potential finding before raising the Advisory, then e-mail us at: renovate-disclosure@mend.io.