Tinus Mørch Abell
2abd139cd2
* feat(config): add github to gitUrl supportedPlatforms Declare GitHub as a supported platform for the gitUrl option so users can configure ssh/endpoint URL resolution on github.com and GHES. Wiring in the github platform module follows in subsequent commits. Refs: renovatebot/renovate#43086 Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * feat(platform/github): fetch sshUrl from repoInfoQuery Add sshUrl to the GraphQL repository query and to the GhRepo type so the platform can resolve SSH-based git remotes. Typed as nullable to match the gitlab pattern and to allow a missing-field error path. Refs: renovatebot/renovate#43086 Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * feat(platform/github): add getRepoUrl helper Introduce a getRepoUrl helper that returns the repository git URL based on the gitUrl option: - 'ssh' uses the sshUrl from the GraphQL repo response; throws CONFIG_GIT_URL_UNAVAILABLE if not available - 'default' and 'endpoint' build an https URL from the configured endpoint with credentials embedded (current behavior) The helper is unused in this commit; initRepo wiring follows. Refs: renovatebot/renovate#43086 Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * feat(platform/github): support gitUrl in initRepo Destructure gitUrl from RepoParams and replace the inline URL construction with getRepoUrl calls. The working URL uses the fork's ssh_url when running in fork mode, otherwise the GraphQL repo.sshUrl. The upstream URL (used when forkCreation and a parentRepo is set) uses repo.sshUrl, which is the parent's URL because the GraphQL query runs before the fork swap. GhRestRepo gains an ssh_url field so findFork/createFork responses can carry the fork's SSH URL forward. Refs: renovatebot/renovate#43086 Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * test(platform/github): cover gitUrl branches Add unit tests for getRepoUrl in utils.spec.ts and three integration tests in index.spec.ts that exercise initRepo with gitUrl=ssh: - ssh URL is forwarded to git.initRepo - missing sshUrl with gitUrl=ssh throws CONFIG_GIT_URL_UNAVAILABLE - fork mode uses the fork's ssh_url for url and the parent's sshUrl for upstreamUrl initRepoMock and forkInitRepoMock now include sshUrl in the GraphQL response so existing tests continue to populate the field that the new code path reads. Refs: renovatebot/renovate#43086 Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * docs: note github-specific gitUrl behavior Document that 'default' and 'endpoint' produce the same URL on GitHub, that 'ssh' uses the repository's sshUrl, and that fork mode propagates SSH selection to both the working URL and the upstream URL. Refs: renovatebot/renovate#43086 Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * refactor(platform/github): pass parsed URL to getRepoUrl Accept a pre-parsed URL in getRepoUrl instead of re-parsing the endpoint string inside the helper. The endpoint is validated during initPlatform so the helper no longer needs its own null check. The caller now parses once and passes the URL to both initRepo call sites; the helper clones it before mutating. Also assert config.repository as non-null at the initRepo call site, fixing the TS2345 error reported by the lint-other job. * Update docs/usage/self-hosted-configuration.md Co-authored-by: Michael Kriese <michael.kriese@gmx.de> --------- Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com> Co-authored-by: Michael Kriese <michael.kriese@gmx.de>
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.