mend/renovate-ce-ee

Mend Renovate Documentation & Examples

Mend Renovate Community and Enterprise Editions

This repository contains documentation, release notes and an issue tracker for Mend Renovate Community Edition (Renovate CE) and Mend Renovate Enterprise Edition (Renovate EE).

Documentation

Please view the Markdown docs in this repository.

Download

Mend Renovate CE/EE is distributed via GitHub's Container Registry under the mend GHCR namespace.

License

Use of Mend Renovate CE/EE is bound by Mend's Terms of Service. You can request a license key by submitting the form at https://www.mend.io/renovate-community/. License requests are processed semi-manually so please allow up to three working days to get your license key by email.

The documentation and examples in this repository are MIT-licensed.

Usage

Please see the docs/ and examples/ directories within this repository.

renovate-ce-ee's Issues

worker not running webhook enqueued tasks (GitLab)

We are running a self hosted Enterprise version of Renovate Pro (GitLab) and running version '0.17.0-pre.0'. I have a repo that has already had an onboarding PR from the scheduler and I'm trying to test the webhook functionality of Renovate, and I have a system hook setup as described here.

However, If I merge the onboarding PR or edit the PR, I can see the webhook event in the Renovate logs but I don't see any worker running afterwards. Is there something wrong with my setup? I also noticed that the worker didn't run after adding Renovate_Bot as a Developer even though I can see the enqueue event in the logs.

The tasks enqueued run if they are enqueued by the scheduler (i.e. every hour).

{ 
   "name":"gitlab-webhook-handler",
   "hostname":"renovate-staging-549946668-n5bpk",
   "pid":1,
   "level":30,
   "event":"push",
   "repository":"mgao/onboard-me-2",
   "msg":"Received webhook event",
   "time":"2019-09-20T17:37:59.413Z",
   "v":0
}{ 
   "name":"gitlab-webhook-handler",
   "hostname":"renovate-staging-549946668-n5bpk",
   "pid":1,
   "level":30,
   "result":{ 
      "task":"enqueue",
      "repository":"mgao/onboard-me-2",
      "reason":"master-commit"
   },
   "msg":"Event result",
   "time":"2019-09-20T17:37:59.413Z",
   "v":0
}{ 
   "name":"gitlab-webhook-handler",
   "hostname":"renovate-staging-549946668-n5bpk",
   "pid":1,
   "level":30,
   "event":"merge_request",
   "repository":"mgao/onboard-me-2",
   "msg":"Received webhook event",
   "time":"2019-09-20T17:37:59.424Z",
   "v":0
}{ 
   "name":"gitlab-webhook-handler",
   "hostname":"renovate-staging-549946668-n5bpk",
   "pid":1,
   "level":30,
   "result":{ 
      "task":"enqueue",
      "repository":"mgao/onboard-me-2",
      "reason":"manual-pr-merge"
   },
   "msg":"Event result",
   "time":"2019-09-20T17:37:59.424Z",
   "v":0
}{ 
   "name":"gitlab-webhook-handler",
   "hostname":"renovate-staging-549946668-n5bpk",
   "pid":1,
   "level":30,
   "event":"push",
   "repository":"mgao/onboard-me-2",
   "msg":"Received webhook event",
   "time":"2019-09-20T17:38:00.060Z",
   "v":0
}{ 
   "name":"gitlab-webhook-handler",
   "hostname":"renovate-staging-549946668-n5bpk",
   "pid":1,
   "level":30,
   "repository":"mgao/onboard-me-2",
   "branch":"renovate/configure",
   "msg":"Ignoring bot commit",
   "time":"2019-09-20T17:38:00.060Z",
   "v":0
}

autodiscoverFilter not respected by job scheduler

I'm trying to use 0.17.0, against a self-hosted Gitlab instance

It looks like the scheduler doesn't respect the autodiscoverFilter setting, though I can see it being recognised:

{"name":"renovate","hostname":"pro-1-79b77998df-6bzl2","pid":1,"level":20,"config":{"autodiscover":true, ...... ,"token":"***********","autodiscoverFilter":"includes*/**"},"msg":"Combined config","time":"2019-10-16T16:36:49.780Z","v":0}

It then looks at all repositories, whether or not they match the filter

(We were hoping to use this to slowly migrate from our current OSS renovate setup)

Support global proxies

Renovate Pro doesn't currently have support for HTTP_PROXY and HTTPS_PROXY environment variables like the CLI tool has.

Support Helm Charts

Perhaps parse any image property in matched yaml files...

Release notes contain mismatched versions and descriptions

What Renovate type are you using?
Renovate Pro

Describe the bug
In a PR generated by Renovate, the version descriptions in the release notes appear to be mismatched.

The latest version is always correct, but previous releases all have descriptions that are off by 1.

Did you see anything helpful in debug logs?
N/A

To Reproduce
N/A

Expected behavior
Screenshot of the dependency's changelog:

Screenshots
Screenshot of the generated PR:

Additional context
Notice in the generated PR, the descriptions for 14.1.0 and 14.0.0 are the same, while in the repo's changelog they are different.

[Github Enterprise] White/black listing of orgs/repos

Use-case: We would like to horizontally scale our Renovate instances, such that we have multiple renovate processes working in parallel that are able to scan over specific orgs on their own, or over certain repos more frequently.

Is this possible?

Massage trailing slash into endpoint

[Question] how to use renovate-approve with renovate-pro

I want to try out https://github.com/apps/renovate-approve with our renovate-pro setup. So far, it seems like renovate-approve doesn't seem to approve any of the renovate-pro PRs. Can you help me to debug this issue?

.npmrc files are not used

No placement of an .npmrc is used by Renovate Pro.

• /home/ubuntu/.npmrc
• /home/<user>/.npmrc
• <project repo>/.npmrc

I am able to correctly npm info <package> from terminal from within the container.

Supporting Corporate Self-signed Certificates

For a company that leverages a self-signed root certificate for managing, and signing, internal certificates for HTTPS, how would, or could, that root certificate be exposed in the Renovate Pro container to enable Renovate, the service, to interact with HTTPS URLs that are using certificates signed by the corporate self-signed certificate?

CLI command to view recent jobs

Specify docker registry?

Is there a way that I can specify a registry for the docker command to use that isn't an assumed domain docker.enterprise.com? We use Artifactory and I would like to point at that for internaly files. If not found there, fallback on the public docker registry.

State Renovate version in all Release Notes

Since Renovate Pro follows a semantic version scheme separate from Renovate, it would be nice if the Renovate Pro docker page provided information on which version of Renovate is contained in each of the images.

Create Kubernetes deployment guide/scripts

Provide all the necessary information and scripts necessary to deploy Renovate Pro to a Kubernetes Cluster.

I like the look of helm and inspired by GitLab's approach: https://docs.gitlab.com/ee/install/kubernetes/gitlab_chart.html

Renovate Pro has quite a lot of configuration though, we should make sure it's not too difficult to include it all.

Issue configuring renovatePro with private NPM repositories.

I have read a number of different issues relating to this & I still can't manage to get it configured correctly.

• renovatebot/renovate#3551
• renovatebot/renovate#851

Config

RENOVATE_persistRepoData=true
RENOVATE_trustLevel=high
GITHUB_APP_ID=12345
LICENSE_NAME=MyCompany
RENOVATE_ENDPOINT=https://api.github.com/
RENOVATE_PLATFORM=github
SCHEDULER_CRON=*/2 06-19 * * 1-5
ACCEPT_AGREEMENT=y
LICENSE_MODE=commercial
RENOVATE_SECRET=<SECRET>
RENOVATE_npmToken=<NPM_TOKEN>
NPM_TOKEN=<NPM_TOKEN>

I have tried some combinations of these:

• only RENOVATE_npmToken
• NPM_TOKEN & trustLevel

I have pulled this information from the following:
https://docs.renovatebot.com/pro/configuration-github/

Thanks

New Release

Hi,
whats the roadmap for future pro releases?
We are waiting for a few bug fixes and in particular for the new regex manager feature.
Is there an way to manually update the renovate version inside the pro image?

Thx a lot

Manual enqueuing of repository

Support a CLI command to add a repository to the job queue with high priority. i.e. "Renovate repository x now".

Renovate tries to update an older version of dependency.

Our renovate tries to update json-schema-faker from ~0.5.0-rc16 -> ~0.5.0-rc9

Clarifying Questions Around Deployment in AWS.

Hello!

I have some clarifying questions because my team is looking to adopt this infrastructure at scale.

1. What is the recommended size of the EC2 instance for running this service?
2. Can we put this service in an AWS Auto Scaling group with multiple nodes that we then balance behind a load balancer to handle high volumes of traffic?
3. Are there any examples of a Kubernetes deployment that could be provided as a starting point?
4. Are there any "blessed" Terraform or CloudFormation configs for deploying this in a viable way at scale?

Not to worry if these things don't exist yet, I'm happy to be the first to do them. Just trying to figure out the details before jumping in.

Global renovate.json config

Does the ability to supply global config (renovate.json) exist?

Is it possible to have multiple hostRules for docker depending on the registry?

Support GitHub Enterprise hosted Presets

1. Single renonvate.json file existing in a GHE repo
2. Project repo with a renovate.json > { "extends": [ "github>ORG/REPOSITORY" ] }

INFO: Repository has invalid config (repository=###/###)
"error": {
    "validationError": "Cannot find preset's package (github>ORG/REPOSITORY)"
}

Assuming Pro uses the same source; the GitHub api url assumes github.com:

renovate/lib/datasource/github/index.js

async function fetchJSONFile(repo, fileName) {
    const url = `https://api.github.com/repos/${repo}/contents/${fileName}`;

Not discovering all repositories

I'm trying to use 0.17.0, against a self-hosted Gitlab instance

It doesn't appear to be handling pagination properly when getting the list of projects:

{"name":"renovate","hostname":"pro-1-79b77998df-6bzl2","pid":1,"level":30,"msg":"jobScheduler running","time":"2019-10-16T16:37:00.002Z","v":0}
{"name":"renovate","hostname":"pro-1-79b77998df-6bzl2","pid":1,"level":30,"msg":"Ignoring non-installed repo","time":"2019-10-16T16:37:04.793Z","v":0}
{"name":"renovate","hostname":"pro-1-79b77998df-6bzl2","pid":1,"level":30,"msg":"Discovered 100 repositories","time":"2019-10-16T16:37:05.115Z","v":0}

Looks like it only finds one page of results?

Gitlab webhook not working

If I check the "If you want to rebase/retry ths MR, check this box" checkbox in an renovate MR, the event gets ignored:

Received webhook event (repository=repo)
"event": "merge_request"
INFO: Ignoring unimportant MR update

PrHourlyLimit is always keeping the value of 2

Hello

while running pro:0.18.0-pre.2 as part of the config.js file I am setting the value of

prHourlyLimit: 6

and I end with a combined config like:

Combined config
server_1  |        "config": {
server_1  |          "platform": "github",
server_1  |          "logFileLevel": "info",
server_1  |          "logLevel": "debug",
server_1  |          "prHourlyLimit": 6,
server_1  |          "baseDir": "/tmp/renovate/",
server_1  |          "token": "***********",
server_1  |          "cacheDir": "/tmp/renovate/cache/",
server_1  |          "githubAuthor": "author<[email protected]>",
server_1  |          "onboarding": true,
server_1  |          "onboardingConfig": {"extends": ["config:base"]},
server_1  |          "endpoint": "https://api.github.com/"
server_1  |        }

yet, in the debug log I keep seeing DEBUG: PR hourly limit remaining: 2 no matter if I change the 6 by a 0 it always keeps using 2

UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'body' of undefined

Starting process with command: `node server`
INFO: Renovate Pro starting
INFO: Renovate Pro is running in Evaluation mode
INFO: Using GitHub endpoint: https://github.example.com/api/v3
INFO: Read private key from disk
 (node:20) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'body' of undefined
   at validateInputs (/usr/src/app/server.js:1:13967)
   at <anonymous>
   at process._tickCallback (internal/process/next_tick.js:188:7)
 (node:20) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
 (node:20) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

I have the environment variable GITHUB_APP_KEY set according to the configuration instructions, so I would assume Renovate would not try reading the key from disk.

Of course, that may, or may not be related at all to the error.

Support for endpoint which triggers a Renovate run

This would be helpful during the process of onboarding repositories. Instead of waiting up to an hour or changing Renovate's cron configuration, hitting an endpoint would force Renovate to run, speeding up the time it takes to onboard a repository.

Renovate Not updating Terraform Providers

Which Renovate are you using?

Renovate Pro

Which platform are you using?

GitHub.com

Have you checked the logs? Don't forget to include them if relevant

Yes:
https://github.com/moredhel/devops-test-repo/blob/master/renovate.log

What would you like to do?

I am trying to maintain the terraform provider versions, but they are not being managed.
I have put together a simple repo which I am testing against:

https://github.com/moredhel/devops-test-repo/, it is a copy of an internal testing repo on my org. But it doesn't seem to be working.

As mentioned in the logs, it finds the provider.tf file, but doesn't find anything to update in it.

Content Trust

Employ Content Trust for signing Renovate Pro release tags (and perhaps latest as well, since that tag is used quite often for early testing).

Webhook for Renovate config updates

Trigger job if non-Renovate PR created or updated and it has Renovate in title or branch name and modified any Renovate config files

[Question] Is there any way to specify CLI version on renovate server?

Now the CLI version seems to be fixed on the server of renovate pro.

I know that it is for stability of Enterprise users. But there is a case that I want to use the latest feature of renovate CLI on my responsibility.

So it will help if I can specify CLI version of renovate pro (e.g. by docker environment variable). Is there any way to do it?

Support BitBucket server

This issue will be used to track the requirements and progress for supporting BitBucket Server (i.e. on-prem/self-hosted).

Please +1 if you're interested in it and would like to track progress.

Support autodiscoverFilter for GitHub

Port Binding

Noticing the following:

Web process failed to bind to $PORT within 60 seconds of launch

The compose example specifically maps to port 8080, but in our environment the port is set dynamically.

Does Renovate Pro check $PORT, or could it check $PORT?

Support self-hosted GitLab

This issue is for tracking GitLab support in Renovate Pro.

Configuration:

• We can determine the platform type based on whether GITHUB_ENDPOINT or GITLAB_ENDPOINT is present
• Will use a GITLAB_TOKEN

Scheduler:

• Will need to use the "getRepos" function, same as --autodiscover

Webhook listener:

• We need to work out a feasible way to configure webhooks for each repository
• Adding project hooks: https://docs.gitlab.com/ce/api/projects.html#add-project-hook

Also, rate limiting for a single token is of concern.

[Question] Is there any way to use dashboard on Renovate Pro?

I am investigating Renovate Pro to use with GitHub Enterprise. It works well but there seems no dashboard like the one renovate on cloud provides.

https://renovatebot.com/dashboard

Is there any way to use the dashboard on Renovate Pro?

GitLab onboarding webhooks

Currently onboarding of new GitLab repos will be triggered hourly when the scheduler does its sync.

We should support handling the GitLab user_add_to_team event for cases where the Renovate user is given new access rights and onboard the repo(s) immediately.

Support using `config.js` instead of `RENOVATE_*` variables

As per documentation and confirmed in #46 (comment), Renovate Pro's validation requires RENOVATE_ENDPOINT to be set in env only, for example.

Therefore this feature request is to allow the use of config.js for env config.

Package Manager Configuration

How do I inject package manager configuration into the Renovate image using the Compose deployment method, or for a Heroku-like platform?

Action Required: Fix Renovate Configuration

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: Preset name not found within published preset config (monorepo:angularmaterial). Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.

Add Heartbeat endpoint

For Docker/k8s/etc it is useful if the Renovate container can answer 200 OK to heartbeat messages when it thinks it's alive. Easiest way to do this is to add a new endpoint to the webhook HTTP server.

ERROR: Cannot apply DB migrations

getting the following error after upgrading from renovate/pro:0.16.0-pre.2 to renovate/pro:0.16.2, looks like a syntax error in the DB connection string:

 INFO: Connected to DB
ERROR: Cannot apply DB migrations
       "err": {
         "name": "error",
         "length": 90,
         "severity": "ERROR",
         "code": "42601",
         "position": "38",
         "file": "scan.l",
         "line": "1127",
         "routine": "scanner_yyerror",
         "appliedMigrations": [],
         "message": "syntax error at or near \";\"",
         "stack": "error: syntax error at or near \";\"\n    at Connection.parseE (/usr/src/app/node_modules/pg/lib/connection.js:602:11)\n    at Connection.parseMessage (/usr/src/app/node_modules/pg/lib/connection.js:399:19)\n    at Socket.<anonymous> (/usr/src/app/node_modules/pg/lib/connection.js:121:22)\n    at Socket.emit (events.js:198:13)\n    at addChunk (_stream_readable.js:288:12)\n    at readableAddChunk (_stream_readable.js:269:11)\n    at Socket.Readable.push (_stream_readable.js:224:10)\n    at TCP.onStreamRead (internal/stream_base_commons.js:94:17)"
       },
       "message": "syntax error at or near \";\""

so far we've reverted back to renovate/pro:0.16.0-pre.2 which doesn't have the issue. the connection parameters are provided by the env vars PGHOST, PGUSER, PGPASSWORD, and PGDATABASE.

Support PostgreSQL Database credentials via DATABASE_URL Environment Variable

We would like to deploy the Renovate Pro image on a Heroku-like Docker platform.

During provisioning of a PostgreSQL database on our infrastructure, a DATABASE_URL environment variable is exposed to the container.

DATABASE_URL contains all necessary credentials to connect to our PostgreSQL database.

Issue PRO vs CLI, private docker registry login

Hi,

I'm trying to setup the docker pro image for our organization, everything goes well, except that it can't connect to our private docker repository, i've tried different versions of Renovate pro without success, however if i setup the CLI versions docker, it connects correctly to the private registry, would you mind to point me in the right direction?, i'm using the same configuration for both containers.

Pro versions used: 0.18.0-pre.2, 0.17.0, 0.16.2
CLI versions used: 19.65.9, 19.59.1, 19.52.2

DEBUG: Combined config

"config": {
         "platform": "github",
         "logFileLevel": "warn",
         "logLevel": "debug",
         "baseDir": "/tmp/renovate/",
         "cacheDir": "/tmp/renovate/cache/",
         "gitAuthor": "Engineering Services Bot <..>",
         "gitPrivateKey": "***********",
         "onboarding": false,
         "onboardingConfig": {"extends": ["config:base"]},
         "hostRules": [
           {
             "hostType": "docker",
             "hostName": "artifacts....",
             "username": "robot...",
             "password": "***********"
           }
         ],
         "endpoint": "https://api.github.com/"
       }

Error trace:

"body": {
           "errors": [
             {
               "code": "UNAUTHORIZED",
               "message": "authentication required",
               "detail": [
                 {
                   "Type": "repository",
                   "Class": "",
                   "Name": "....",
                   "Action": "pull"
                 }
               ]
             }
           ]
         },
         "message": "Response code 401 (Unauthorized)",
         "stack": "HTTPError: Response code 401 (Unauthorized)\n    at EventEmitter.emitter.on (/usr/src/app/node_modules/got/source/as-promise.js:74:19)\n    at process._tickCallback (internal/process/next_tick.js:68:7)"

Deprioritize Onboarding PRs in the Scheduler

What would you like Renovate to be able to do?
In Enterprise (and I assume this applies to public), if a repo has an onboarding PR open that is never merged, don't weight that as much as a repo that has been onboarded.

Describe the solution you'd like
Right now, if you have thousands of repos that don't onboard the onboarding PR, renovate will treat them equally and schedule them along with the fully onboarded repos. At scale, we may have stale repos in an org that aren't maintained. This means we are losing time as renovate tries to schedules hundreds of unonboarded repos.

Describe alternatives you've considered
N/A

Additional context
N/A

Manage App Description

Have the Renovate Pro service manage the description field for the GitHub App on a GHE deployment.

We wrote our own, based quite a bit on a copy&paste of the official Renovate App, but I'd really like to see the description managed for us. The description field is a great way to sell Renovate to our internal engineering community.

Gitlab self hosted projects from nested groups are ignored

Which Renovate are you using? x the right box:

• Renovate Open Source CLI
• WhiteSource Renovate App
• Renovate Pro
• Other (please write below)

Which platform are you using? x the right box:

• GitHub.com
• GitHub Enterprise
• GitLab.com
• GitLab self-hosted
• Bitbucket Server
• Bitbucket Cloud
• Azure DevOps

Have you checked the logs? Don't forget to include them if relevant

ubuntu@gitlab:~$ docker service logs -f renovate_renovate
renovate_renovate.1.2f1x6um7e0x2@gitlab    |  INFO: Initializing server container                   
renovate_renovate.1.2f1x6um7e0x2@gitlab    |  INFO: Running in commercial license mode
renovate_renovate.1.2f1x6um7e0x2@gitlab    |  INFO: License name: MYIO            
renovate_renovate.1.2f1x6um7e0x2@gitlab    |  INFO: Trying gitlab platform: REDACTED
renovate_renovate.1.2f1x6um7e0x2@gitlab    |  INFO: Using GitLab endpoint: REDACTED
renovate_renovate.1.2f1x6um7e0x2@gitlab    |  INFO: Authenticated as GitLab user: renovate-bot      
renovate_renovate.1.2f1x6um7e0x2@gitlab    |  INFO: jobScheduler running                                                                          
renovate_renovate.1.2f1x6um7e0x2@gitlab    |  INFO: Discovered 17 repositories                    
renovate_renovate.1.2f1x6um7e0x2@gitlab    |  INFO: Repository list from scheduler         
renovate_renovate.1.2f1x6um7e0x2@gitlab    |        "repos": [                                               
renovate_renovate.1.2f1x6um7e0x2@gitlab    |          "myio/renovate", 
[redacted repo list]                                
renovate_renovate.1.2f1x6um7e0x2@gitlab    |        ]                                                
renovate_renovate.1.2f1x6um7e0x2@gitlab    |  INFO: Using cron schedule: 0 * * * *
renovate_renovate.1.2f1x6um7e0x2@gitlab    |  INFO: Job scheduler started         
renovate_renovate.1.2f1x6um7e0x2@gitlab    |  INFO: Job worker started               
renovate_renovate.1.2f1x6um7e0x2@gitlab    |  INFO: Initialized GitLab webhook handler
renovate_renovate.1.2f1x6um7e0x2@gitlab    |  INFO: Webhook listener bound to port 8080 

later

renovate_renovate.1.2f1x6um7e0x2@gitlab    |  INFO: Repository has changed during renovation - aborting (repository=myio/renovate)

What would you like to do?

I've added the Renovate user to the team and it does detect the repos, but won't create the onboarding PR. If I run the non-pro renovate from cli (with --dry-run) it says it would create PRs right away while the pro version won't create PRs even if you trigger it through the webhook (for instance, by removing the bot from the team and adding to a single repository (because team adds don't trigger the autodiscover feature it seems)), it always says the repository has changed during the renovation, even though it didn't. Bellow is everything I used to deploy renovate:

docker-compose.yml

version: '3.7'

configs:
  config.js:
    name: config.js_${HASH:-undefined}
    file: config.js

volumes:
  tmp:

services:
  renovate:
    image: renovate/pro:0.18.0
    environment:
      - ACCEPT_AGREEMENT=y
      - LICENSE_MODE=commercial
      - LICENSE_NAME
      - RENOVATE_PLATFORM=gitlab
      - RENOVATE_ENDPOINT
      - RENOVATE_TOKEN # Personal Access Token for bot account
      - GITHUB_COM_TOKEN # Personal Access Token for github.com (used for retrieving changelogs)
      - WEBHOOK_SECRET # Optional, default to 'renovate'
      - SCHEDULER_CRON # Optional, defaults to '0 * * * *' (hourly)
    ports:
      - "8080:8080"
    volumes:
      - "tmp:/tmp" # Use a volume for this as the cache will cause a lot of churn
    configs:
      - source: config.js
        target: /usr/src/webapp/config.js

config.js

module.exports = {
  autodiscover: 'true',
  logLevel: 'info',
  requireConfig: true,
  onboarding: true,
  onboardingConfig: {
    extends: [
      'config:base',
      'preview:dockerCompose'
    ],
    separateMinorPatch: true,
    packageRules: [
      {
        updateTypes: ['patch'],
        automerge: true,
        automergeType: 'branch'
      },
      {
        updateTypes: ['major', 'minor'],
        automerge: false
      }
    ]
  }
}

.gitlab-ci.yml

stages:
  - deploy

variables:
  HASH: ${CI_COMMIT_SHORT_SHA}

deploy:
  image: docker:latest
  tags:
    - renovate
  stage: deploy
  script:
    - docker stack deploy renovate -c docker-compose.yml

[Question] Define dependency chains between repositories

Which Renovate are you using? e.g. CLI, GitHub app, GitLab app, etc.

pro on premise

Which platform are you using? GitHub, GitLab, Bitbucket Azure DevOps

gitlab

What is your question?

If i have 2 repositories A B
B uses Artifacts built by A
is there a way to trigger a renovate run in B if a new master pipeline in A is successful?

Thx a lot

[Questsion] Renovate-pro does not rebase PR on demand

After upgraded to the latest 0.18.0 renovate( including removing the postgres in our deployment), we notice that renovate-pro doesn't really rebase our PR on demand after it started for like 30 minutes. We would see the rebase-request enqueue, but then renovate would not consume that queue item.

We delete the renovate-pro pod to see if it solves the problem, and renovate seems to be responsive again to rebase our PR but after 15 to 30 minutes, the same problem persist.

Is there a way for us to test/debug this problem?

Add option to log "Dependency Lookup Failure"s as errors

Which Renovate are you using?

Renovate Pro v0.18.5

Which platform are you using?

Enterprise GitHub

Have you checked the logs? Don't forget to include them if relevant

Yes

INFO: Dependency lookup failure: unauthorized (repository=${MY_ORG}/${MY_REPO})
       "pkgUrl": "${CORPORATE_ARTYLAB_LINK}",
       "authInfoType": "Basic",
       . . .
       "statusCode": 403,
       "statusMessage": "Forbidden",
       . . .

What would you like to do?

I believe dependency lookup failures should be logged as ERROR rather than as INFO, at least for certain responses from package sources like 403 Forbidden.

Scans reaching some invisible limit on big organizations

Hi, this might not be a renovate issue but a configuration one, the thing is that we have over 2000 repositories to be scanned by a single renovate instance, which has enough resources to compute that batch, but according to logs we can see it is scanning about 400 repos every hour