search

renovatebot / config-help

Please use the Discussions feature of https://github.com/renovatebot/renovate instead
https://github.com/renovatebot/renovate/discussions
MIT License
27 stars 16 forks source link

[Question] Why is Renovate flapping between two patches when updating a PR? #374

Closed aiwilliams closed 5 years ago

aiwilliams commented 5 years ago

Which Renovate are you using? CLI, App, or Pro

CLI

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

Bitbucket

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

13:18:32  INFO: Renovating repository (repository=lifeomic/jupiter-integration-jira)
13:18:32  INFO: Initialising git repository into /tmp/renovate/repos/bitbucket/lifeomic/jupiter-integration-jira (repository=lifeomic/jupiter-integration-jira)
13:18:33  INFO: git clone completed (repository=lifeomic/jupiter-integration-jira)
13:18:33        "cloneSeconds": 1.2
13:18:33  INFO: Setting git author (repository=lifeomic/jupiter-integration-jira)
13:18:33        "gitAuthor": {"name": "Renovate Bot", "email": "bitbucket@lifeomic.com"}
13:18:41  INFO: Retrieved Pull Requests (repository=lifeomic/jupiter-integration-jira)
13:18:41        "length": 52
13:18:41  WARN: Error finding issues (repository=lifeomic/jupiter-integration-jira)
13:18:41  INFO: Repository config (repository=lifeomic/jupiter-integration-jira)
13:18:41        "configFile": ".renovaterc.json",
13:18:41        "config": {"extends": ["github>JupiterOne/renovate-config:managedIntegrationDeployment"]}
13:18:42  INFO: Found dockerfile package files (repository=lifeomic/jupiter-integration-jira)
13:18:42  INFO: Found npm package files (repository=lifeomic/jupiter-integration-jira)
13:18:42  INFO: Found terraform package files (repository=lifeomic/jupiter-integration-jira)
13:18:43  INFO: Processing 3 branches: renovate/deps, renovate/devdeps, renovate/major-devdeps (repository=lifeomic/jupiter-integration-jira)
13:19:12  INFO: Performing lockfileUpdate (yarn) (repository=lifeomic/jupiter-integration-jira, dependencies=@lifeomic/lambda-tools,@lifeomic/typescript-tools,@types/aws-lambda,@types/node, branch=renovate/devdeps)
13:19:22  INFO: Generated lockfile (repository=lifeomic/jupiter-integration-jira, dependencies=@lifeomic/lambda-tools,@lifeomic/typescript-tools,@types/aws-lambda,@types/node, branch=renovate/devdeps)
13:19:22        "seconds": 36,
13:19:22        "type": "yarn.lock",
13:19:22        "stdout": "yarn install v1.15.2\n[1/4] Resolving packages...\n[2/4] Fetching packages...\n[3/4] Linking dependencies...\n[4/4] Building fresh packages...\nDone in 25.68s.\nyarn upgrade v1.15.2\n[1/4] Resolving packages...\n[2/4] Fetching packages...\n[3/4] Linking dependencies...\n[4/4] Rebuilding all packages...\nsuccess Saved lockfile.\nsuccess Saved 1 new dependency.\ninfo Direct dependencies\n└─ @types/node@8.10.54\ninfo All dependencies\n└─ @types/node@8.10.54\nDone in 9.56s.\n",
13:19:22        "stderr": "warning \"@lifeomic/lambda-runtime-tools > apollo-cache-inmemory@1.6.2\" has unmet peer dependency \"graphql@0.11.7 || ^0.12.0 || ^0.13.0 || ^14.0.0\".\nwarning \"@lifeomic/lambda-runtime-tools > apollo-client@2.6.3\" has unmet peer dependency \"graphql@^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0\".\nwarning \"@lifeomic/lambda-runtime-tools > apollo-link-http@1.5.15\" has unmet peer dependency \"graphql@^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0\".\nwarning \"@lifeomic/lambda-runtime-tools > apollo-cache-inmemory > apollo-utilities@1.3.2\" has unmet peer dependency \"graphql@^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0\".\nwarning \"@lifeomic/lambda-runtime-tools > apollo-client > apollo-link@1.2.12\" has unmet peer dependency \"graphql@^0.11.3 || ^0.12.3 || ^0.13.0 || ^14.0.0\".\nwarning \"@lifeomic/lambda-runtime-tools > apollo-link-http > apollo-link-http-common@0.2.14\" has unmet peer dependency \"graphql@^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0\".\nwarning Ignored scripts due to flag.\nwarning \"@lifeomic/lambda-runtime-tools > apollo-cache-inmemory@1.6.2\" has unmet peer dependency \"graphql@0.11.7 || ^0.12.0 || ^0.13.0 || ^14.0.0\".\nwarning \"@lifeomic/lambda-runtime-tools > apollo-client@2.6.3\" has unmet peer dependency \"graphql@^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0\".\nwarning \"@lifeomic/lambda-runtime-tools > apollo-link-http@1.5.15\" has unmet peer dependency \"graphql@^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0\".\nwarning \"@lifeomic/lambda-runtime-tools > apollo-cache-inmemory > apollo-utilities@1.3.2\" has unmet peer dependency \"graphql@^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0\".\nwarning \"@lifeomic/lambda-runtime-tools > apollo-client > apollo-link@1.2.12\" has unmet peer dependency \"graphql@^0.11.3 || ^0.12.3 || ^0.13.0 || ^14.0.0\".\nwarning \"@lifeomic/lambda-runtime-tools > apollo-link-http > apollo-link-http-common@0.2.14\" has unmet peer dependency \"graphql@^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0\".\nwarning Ignored scripts due to flag.\n"
13:19:27  WARN: Error finding issues (repository=lifeomic/jupiter-integration-jira)
13:19:29  INFO: Finished repository (repository=lifeomic/jupiter-integration-jira)
13:58:52  INFO: Renovating repository (repository=lifeomic/jupiter-integration-jira)
13:58:52  INFO: Initialising git repository into /tmp/renovate/repos/bitbucket/lifeomic/jupiter-integration-jira (repository=lifeomic/jupiter-integration-jira)
13:58:53  INFO: git clone completed (repository=lifeomic/jupiter-integration-jira)
13:58:53        "cloneSeconds": 1
13:58:53  INFO: Setting git author (repository=lifeomic/jupiter-integration-jira)
13:58:53        "gitAuthor": {"name": "Renovate Bot", "email": "bitbucket@lifeomic.com"}
13:58:59  INFO: Retrieved Pull Requests (repository=lifeomic/jupiter-integration-jira)
13:58:59        "length": 52
13:58:59  WARN: Error finding issues (repository=lifeomic/jupiter-integration-jira)
13:58:59  INFO: Repository config (repository=lifeomic/jupiter-integration-jira)
13:58:59        "configFile": ".renovaterc.json",
13:58:59        "config": {"extends": ["github>JupiterOne/renovate-config:managedIntegrationDeployment"]}
13:59:00  INFO: Found dockerfile package files (repository=lifeomic/jupiter-integration-jira)
13:59:00  INFO: Found npm package files (repository=lifeomic/jupiter-integration-jira)
13:59:00  INFO: Found terraform package files (repository=lifeomic/jupiter-integration-jira)
13:59:01  INFO: Processing 3 branches: renovate/deps, renovate/devdeps, renovate/major-devdeps (repository=lifeomic/jupiter-integration-jira)
13:59:06  INFO: Need to update package file so will rebase first (repository=lifeomic/jupiter-integration-jira, dependencies=@lifeomic/lambda-tools,@lifeomic/typescript-tools,@types/aws-lambda,@types/node, branch=renovate/devdeps)
13:59:35  INFO: Performing lockfileUpdate (yarn) (repository=lifeomic/jupiter-integration-jira, dependencies=@lifeomic/lambda-tools,@lifeomic/typescript-tools,@types/aws-lambda,@types/node, branch=renovate/devdeps)
13:59:42  INFO: Generated lockfile (repository=lifeomic/jupiter-integration-jira, dependencies=@lifeomic/lambda-tools,@lifeomic/typescript-tools,@types/aws-lambda,@types/node, branch=renovate/devdeps)
13:59:42        "seconds": 36,
13:59:42        "type": "yarn.lock",
13:59:42        "stdout": "yarn install v1.15.2\n[1/4] Resolving packages...\n[2/4] Fetching packages...\n[3/4] Linking dependencies...\n[4/4] Building fresh packages...\nsuccess Saved lockfile.\nDone in 28.05s.\nyarn upgrade v1.15.2\n[1/4] Resolving packages...\n[2/4] Fetching packages...\n[3/4] Linking dependencies...\n[4/4] Rebuilding all packages...\nsuccess Saved lockfile.\nsuccess Saved 1 new dependency.\ninfo Direct dependencies\n└─ @types/node@8.10.54\ninfo All dependencies\n└─ @types/node@8.10.54\nDone in 7.43s.\n",
13:59:42        "stderr": "warning \"@lifeomic/lambda-runtime-tools > apollo-cache-inmemory@1.6.2\" has unmet peer dependency \"graphql@0.11.7 || ^0.12.0 || ^0.13.0 || ^14.0.0\".\nwarning \"@lifeomic/lambda-runtime-tools > apollo-client@2.6.3\" has unmet peer dependency \"graphql@^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0\".\nwarning \"@lifeomic/lambda-runtime-tools > apollo-link-http@1.5.15\" has unmet peer dependency \"graphql@^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0\".\nwarning \"@lifeomic/lambda-runtime-tools > apollo-cache-inmemory > apollo-utilities@1.3.2\" has unmet peer dependency \"graphql@^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0\".\nwarning \"@lifeomic/lambda-runtime-tools > apollo-client > apollo-link@1.2.12\" has unmet peer dependency \"graphql@^0.11.3 || ^0.12.3 || ^0.13.0 || ^14.0.0\".\nwarning \"@lifeomic/lambda-runtime-tools > apollo-link-http > apollo-link-http-common@0.2.14\" has unmet peer dependency \"graphql@^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0\".\nwarning Ignored scripts due to flag.\nwarning \"@lifeomic/lambda-runtime-tools > apollo-cache-inmemory@1.6.2\" has unmet peer dependency \"graphql@0.11.7 || ^0.12.0 || ^0.13.0 || ^14.0.0\".\nwarning \"@lifeomic/lambda-runtime-tools > apollo-client@2.6.3\" has unmet peer dependency \"graphql@^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0\".\nwarning \"@lifeomic/lambda-runtime-tools > apollo-link-http@1.5.15\" has unmet peer dependency \"graphql@^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0\".\nwarning \"@lifeomic/lambda-runtime-tools > apollo-cache-inmemory > apollo-utilities@1.3.2\" has unmet peer dependency \"graphql@^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0\".\nwarning \"@lifeomic/lambda-runtime-tools > apollo-client > apollo-link@1.2.12\" has unmet peer dependency \"graphql@^0.11.3 || ^0.12.3 || ^0.13.0 || ^14.0.0\".\nwarning \"@lifeomic/lambda-runtime-tools > apollo-link-http > apollo-link-http-common@0.2.14\" has unmet peer dependency \"graphql@^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0\".\nwarning Ignored scripts due to flag.\n"
13:59:45  WARN: Error finding issues (repository=lifeomic/jupiter-integration-jira)
13:59:52  INFO: Finished repository (repository=lifeomic/jupiter-integration-jira)

Renovate configs referenced by .renovaterc.json:

Screen Shot 2019-10-01 at 2 19 12 PM Screen Shot 2019-10-01 at 2 15 11 PM Screen Shot 2019-10-01 at 2 16 02 PM

What is your question?

Why does Renovate keep updating this branch with commits that essentially flap between the two patches? What can I do to prevent this?

rarkins commented 5 years ago

First thing I'd look at is to capture at debug level (LOG_LEVEL=debug in env) and diff the packageFiles with updates messages between two of these runs. This will tell you if Renovate is resolving any different versions between runs.

stale[bot] commented 5 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed soon if no further activity occurs.