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

chore: Configure Renovate - autoclosed #114

Closed
wants to merge 1 commit into from
Closed

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Apr 2, 2024

Mend Renovate

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

  • .circleci/config.yml (circleci)
  • package.json (npm)

Configuration Summary

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

  • Start dependency updates only once this onboarding PR is merged
  • Show all Merge Confidence badges for pull requests.
  • Schedule for weekends.
  • 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).
  • Add the renovate/ prefix to all branch names.
  • Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
  • Keep existing branches updated even when not scheduled.
  • Automerge patch and minor upgrades if they pass tests.
  • Ignore node_modules, bower_components, vendor and various test/tests directories.
  • Update existing lock files only when package.json is modified.
  • Limit to maximum 20 open PRs at any time.
  • Group known monorepo packages together.
  • picasso.js monorepo packages
  • after-work.js monorepo packages
  • Group minor and patch updates for all packages in one
  • Group minor and patch updates for all packages in one
  • Run Renovate on following schedule: every weekend

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Pull Request description the next time it runs.


What to Expect

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

chore(deps): update dependency lodash.merge to v4.6.2 [security]
  • Branch name: renovate/npm-lodash.merge-vulnerability
  • Merge into: master
  • Upgrade lodash.merge to 4.6.2
chore(deps): update minor and patch
chore(deps): update circleci/node docker tag to v17
  • Schedule: ["every weekend"]
  • Branch name: renovate/circleci-node-17.x
  • Merge into: master
  • Upgrade circleci/node to 17.2.0-browsers
  • Upgrade circleci/node to 17.2.0
chore(deps): update dependency babel-loader to v9
  • Schedule: ["every weekend"]
  • Branch name: renovate/babel-loader-9.x
  • Merge into: master
  • Upgrade babel-loader to 9.1.3
chore(deps): update dependency css-loader to v6
  • Schedule: ["every weekend"]
  • Branch name: renovate/css-loader-6.x
  • Merge into: master
  • Upgrade css-loader to 6.10.0
chore(deps): update dependency del to v7
  • Schedule: ["every weekend"]
  • Branch name: renovate/del-7.x
  • Merge into: master
  • Upgrade del to 7.1.0
chore(deps): update dependency eslint to v8
  • Schedule: ["every weekend"]
  • Branch name: renovate/eslint-8.x
  • Merge into: master
  • Upgrade eslint to 8.57.0
chore(deps): update dependency eslint-loader to v4
  • Schedule: ["every weekend"]
  • Branch name: renovate/eslint-loader-4.x
  • Merge into: master
  • Upgrade eslint-loader to 4.0.2
chore(deps): update dependency gulp to v5
  • Schedule: ["every weekend"]
  • Branch name: renovate/gulp-5.x
  • Merge into: master
  • Upgrade gulp to 5.0.0
chore(deps): update dependency gulp-zip to v6
  • Schedule: ["every weekend"]
  • Branch name: renovate/gulp-zip-6.x
  • Merge into: master
  • Upgrade gulp-zip to 6.0.0
chore(deps): update dependency less to v4
  • Schedule: ["every weekend"]
  • Branch name: renovate/less-4.x
  • Merge into: master
  • Upgrade less to 4.2.0
chore(deps): update dependency less-loader to v12
  • Schedule: ["every weekend"]
  • Branch name: renovate/less-loader-12.x
  • Merge into: master
  • Upgrade less-loader to 12.2.0
chore(deps): update dependency style-loader to v3
  • Schedule: ["every weekend"]
  • Branch name: renovate/style-loader-3.x
  • Merge into: master
  • Upgrade style-loader to 3.3.4
chore(deps): update dependency stylelint to v16
  • Schedule: ["every weekend"]
  • Branch name: renovate/stylelint-16.x
  • Merge into: master
  • Upgrade stylelint to 16.3.1
chore(deps): update dependency stylelint-webpack-plugin to v5
  • Schedule: ["every weekend"]
  • Branch name: renovate/stylelint-webpack-plugin-5.x
  • Merge into: master
  • Upgrade stylelint-webpack-plugin to 5.0.0
chore(deps): update dependency webpack to v5
  • Schedule: ["every weekend"]
  • Branch name: renovate/webpack-5.x
  • Merge into: master
  • Upgrade webpack to 5.91.0
fix(deps): update react monorepo to v18 (major)
  • Schedule: ["every weekend"]
  • Branch name: renovate/major-react-monorepo
  • Merge into: master
  • Upgrade react to 18.2.0
  • Upgrade react-dom to 18.2.0

🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm 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 Mend Renovate. View repository job log here.

@renovate renovate bot added the renovate label Apr 2, 2024
@renovate renovate bot changed the title chore: Configure Renovate chore: Configure Renovate - autoclosed Apr 7, 2024
@renovate renovate bot closed this Apr 7, 2024
@renovate renovate bot deleted the renovate/configure branch April 7, 2024 02:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants