Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configure Renovate #17

Merged
merged 1 commit into from
Jan 11, 2018
Merged

Configure Renovate #17

merged 1 commit into from
Jan 11, 2018

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 5, 2018

Welcome to Renovate!

This is an onboarding PR to help you understand and configure Renovate before regular Pull Requests begin. Once you merge or close this Pull Request, Renovate will begin keeping your dependencies up-to-date.

If you have any questions, try reading our Docs, particularly the Getting Started section. You can post questions in our Config Help repository or @ the app author @rarkins in this PR and he'll probably see it.


Configuration Summary

Based on the currently configured presets, Renovate will:

  • Start dependency updates once this Configure Renovate PR is merged or closed
  • Separate major versions of dependencies into individual branches/PRs
  • Combine any patch and minor upgrades together into same branch/PR
  • Upgrade to unstable versions only if the existing version is unstable
  • Raise PRs immediately (after branch is created)
  • Use renovate/ as prefix for all branch names
  • If semantic commits detected, use semantic commit type fix for dependencies and chore for all others
  • Keep existing branches updated even when not scheduled
  • Disable automerging feature - wait for humans to merge all PRs
  • Ignore node_modules, bower_components, and various test/tests directories
  • Update existing lock files only when package.json is modified
  • Autodetect whether to pin dependencies or maintain ranges
  • Rate limit PR creation to a maximum of two per hour
  • Preconfigure dependencies where an odd major version indicates unstable (Docker-only)

Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json in this branch and this Pull Request description will be updated the next time Renovate runs. Try to use Config Presets (the extends array) when possible rather than raw config, as then this PR will be able to more accurately describe your settings.


What to Expect

With your current configuration, Renovate will create 7 Pull Requests:

  1. Pin Dependencies
  1. Pin Dockerfile uber/web-base-image:1.0.0 image digest
  • Branch name: renovate/pin-docker-digests
  • Pins uber/web-base-image in Dockerfile to undefined
  1. Update dependency eslint-config-fusion to v0.2.1
  • Branch name: renovate/eslint-config-fusion-0.x
  • Upgrades eslint-config-fusion in devDependencies from ^0.1.2 to 0.2.1
  1. Update dependency flow-bin to v0.63.1
  • Branch name: renovate/flow-bin-0.x
  • Upgrades flow-bin in devDependencies from ^0.59.0 to 0.63.1
  1. Update dependency prettier to v1.10.2
  • Branch name: renovate/prettier-1.x
  • Upgrades prettier in devDependencies from 1.8.2 to 1.10.2
  1. Update uber/web-base-image Dockerfile tag to v1.0.1
  • Branch name: renovate/docker-uber-web-base-image-1.x
  • Upgrades uber/web-base-image in Dockerfile from undefined to 1.0.1
  1. Update dependency create-universal-package to v3
  • Branch name: renovate/create-universal-package-3.x
  • Upgrades create-universal-package in devDependencies from ^2.1.1 to 3.2.4

@codecov-io
Copy link

codecov-io commented Jan 5, 2018

Codecov Report

Merging #17 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master      #17   +/-   ##
=======================================
  Coverage   93.61%   93.61%           
=======================================
  Files           6        6           
  Lines          47       47           
  Branches       10       10           
=======================================
  Hits           44       44           
  Misses          1        1           
  Partials        2        2

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b8ad804...451e326. Read the comment docs.

@renovate renovate bot force-pushed the renovate/configure branch 3 times, most recently from b43e185 to 48499a8 Compare January 11, 2018 19:30
@KevinGrandon
Copy link
Contributor

!merge

@old-fusion-bot old-fusion-bot bot merged commit 40d8594 into master Jan 11, 2018
@renovate renovate bot deleted the renovate/configure branch January 11, 2018 23:08
@renovate
Copy link
Contributor Author

renovate bot commented May 12, 2019

Renovate is disabled

Renovate is disabled because there is no Renovate configuration file. To enable Renovate, you can either (a) change this PR's title to get a new onboarding PR, and merge the new onboarding PR, or (b) create a Renovate config file, and commit that file to your base branch.

@rarkins
Copy link

rarkins commented May 12, 2019

@KevinGrandon this repo needs a renovate.json. Need help adding one?

@KevinGrandon
Copy link
Contributor

KevinGrandon commented May 13, 2019

@KevinGrandon this repo needs a renovate.json. Need help adding one?

Thanks for the ping :) Things are a bit crazy now because we're moving into a monorepo, and did so by renaming an existing repo. We'll have to update our configs to work with this monorepo structure, it should be an interesting experiment.

Trying this in: #374

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants