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 #366

Closed
wants to merge 1 commit into from
Closed

Configure Renovate #366

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 25, 2019

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.


Detected Package Files

  • app/package.json (npm)
  • package.json (npm)

Configuration Summary

Based on the default config's presets, Renovate will:

  • Start dependency updates only once this Configure Renovate PR is merged
  • Separate major versions of dependencies into individual branches/PRs
  • Do not separate patch and minor upgrades into separate PRs for the same dependency
  • 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, vendor 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
  • Limit to maximum 20 open PRs at any time
  • Group known monorepo packages together
  • Use curated list of recommended non-monorepo package groupings

🔡 Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json in this branch with your custom config and the list of Pull Requests in the "What to Expect" section below will be updated the next time Renovate runs.


You have configured Renovate to use branch master as base branch.

What to Expect

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

chore(deps): update dependency babel-plugin-react-intl to v4.1.14
  • Schedule: "at any time"
  • Branch name: renovate/babel-plugin-react-intl-4.x
  • Merge into: master
  • Upgrade babel-plugin-react-intl to 4.1.14
chore(deps): update dependency electron to v5.0.10
  • Schedule: "at any time"
  • Branch name: renovate/electron-5.x
  • Merge into: master
  • Upgrade electron to 5.0.10
chore(deps): update dependency eslint-config-precure to v4.18.1
  • Schedule: "at any time"
  • Branch name: renovate/eslint-config-precure-4.x
  • Merge into: master
  • Upgrade eslint-config-precure to 4.18.1
chore(deps): update dependency extract-react-intl-messages to v1.1.0
  • Schedule: "at any time"
  • Branch name: renovate/extract-react-intl-messages-1.x
  • Merge into: master
  • Upgrade extract-react-intl-messages to 1.1.0
chore(deps): update dependency flow-bin to v0.106.1
  • Schedule: "at any time"
  • Branch name: renovate/flow-bin-0.x
  • Merge into: master
  • Upgrade flow-bin to 0.106.1
chore(deps): update dependency react-hot-loader to v4.12.11
  • Schedule: "at any time"
  • Branch name: renovate/react-hot-loader-4.x
  • Merge into: master
  • Upgrade react-hot-loader to 4.12.11
chore(deps): update dependency react-test-renderer to v16.9.0
  • Schedule: "at any time"
  • Branch name: renovate/react-monorepo
  • Merge into: master
  • Upgrade react-test-renderer to 16.9.0
chore(deps): update dependency webpack to v4.39.2
  • Schedule: "at any time"
  • Branch name: renovate/webpack-4.x
  • Merge into: master
  • Upgrade webpack to 4.39.2
chore(deps): update dependency webpack-cli to v3.3.7
  • Schedule: "at any time"
  • Branch name: renovate/webpack-cli-3.x
  • Merge into: master
  • Upgrade webpack-cli to 3.3.7
chore(deps): update dependency webpack-dev-server to v3.8.0
  • Schedule: "at any time"
  • Branch name: renovate/webpack-dev-server-3.x
  • Merge into: master
  • Upgrade webpack-dev-server to 3.8.0
chore(deps): update jest monorepo to v24.9.0
  • Schedule: "at any time"
  • Branch name: renovate/jest-monorepo
  • Merge into: master
  • Upgrade babel-jest to 24.9.0
  • Upgrade jest to 24.9.0
fix(deps): update dependency electron-context-menu to ^0.14.0
  • Schedule: "at any time"
  • Branch name: renovate/electron-context-menu-0.x
  • Merge into: master
  • Upgrade electron-context-menu to ^0.14.0
chore(deps): update dependency babel-plugin-react-intl-auto to v2
  • Schedule: "at any time"
  • Branch name: renovate/babel-plugin-react-intl-auto-2.x
  • Merge into: master
  • Upgrade babel-plugin-react-intl-auto to 2.2.0
chore(deps): update dependency electron to v6
  • Schedule: "at any time"
  • Branch name: renovate/electron-6.x
  • Merge into: master
  • Upgrade electron to 6.0.4
chore(deps): update dependency eslint to v6
  • Schedule: "at any time"
  • Branch name: renovate/eslint-6.x
  • Merge into: master
  • Upgrade eslint to 6.2.2
chore(deps): update dependency eslint-config-precure to v5
  • Schedule: "at any time"
  • Branch name: renovate/eslint-config-precure-5.x
  • Merge into: master
  • Upgrade eslint-config-precure to 5.0.2
chore(deps): update dependency execa to v2
  • Schedule: "at any time"
  • Branch name: renovate/execa-2.x
  • Merge into: master
  • Upgrade execa to 2.0.4
chore(deps): update dependency extract-react-intl-messages to v2
  • Schedule: "at any time"
  • Branch name: renovate/extract-react-intl-messages-2.x
  • Merge into: master
  • Upgrade extract-react-intl-messages to 2.2.1
chore(deps): update dependency file-loader to v4
  • Schedule: "at any time"
  • Branch name: renovate/file-loader-4.x
  • Merge into: master
  • Upgrade file-loader to 4.2.0
chore(deps): update dependency husky to v3
  • Schedule: "at any time"
  • Branch name: renovate/husky-3.x
  • Merge into: master
  • Upgrade husky to 3.0.4
chore(deps): update dependency lint-staged to v9
  • Schedule: "at any time"
  • Branch name: renovate/lint-staged-9.x
  • Merge into: master
  • Upgrade lint-staged to 9.2.4
chore(deps): update dependency url-loader to v2
  • Schedule: "at any time"
  • Branch name: renovate/url-loader-2.x
  • Merge into: master
  • Upgrade url-loader to 2.1.0
chore(deps): update dependency yaml-flat-loader to v1
  • Schedule: "at any time"
  • Branch name: renovate/yaml-flat-loader-1.x
  • Merge into: master
  • Upgrade yaml-flat-loader to 1.0.1
fix(deps): update dependency camelcase-keys to v6
  • Schedule: "at any time"
  • Branch name: renovate/camelcase-keys-6.x
  • Merge into: master
  • Upgrade camelcase-keys to ^6.0.0
fix(deps): update dependency electron-debug to v3
  • Schedule: "at any time"
  • Branch name: renovate/electron-debug-3.x
  • Merge into: master
  • Upgrade electron-debug to ^3.0.0
fix(deps): update dependency react-intl to v3
  • Schedule: "at any time"
  • Branch name: renovate/react-intl-3.x
  • Merge into: master
  • Upgrade react-intl to ^3.0.0

🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or spam the project. See docs for prhourlylimit for details.


❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.


This PR has been generated by Renovate Bot. View repository job log here.

@akameco akameco closed this Aug 25, 2019
@akameco akameco deleted the renovate/configure branch August 25, 2019 18:21
@renovate
Copy link
Contributor Author

renovate bot commented Aug 25, 2019

Renovate is disabled

Renovate is disabled due to lack of config. If you wish to reenable it, you can either (a) commit a config file to your base branch, or (b) rename this closed PR to trigger a replacement onboarding PR.

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.

2 participants