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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Configure Renovate #2

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Mar 9, 2022

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

  • 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.
  • Enable Renovate Dependency Dashboard creation.
  • Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
  • Ignore node_modules, bower_components, vendor and various test/tests directories.
  • Group known monorepo packages together.
  • Use curated list of recommended non-monorepo package groupings.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.

🔡 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 16 Pull Requests:

Update dependency script-ext-html-webpack-plugin to v2.1.5
  • Schedule: ["at any time"]
  • Branch name: renovate/script-ext-html-webpack-plugin-2.x-lockfile
  • Merge into: main
  • Upgrade script-ext-html-webpack-plugin to 2.1.5
Update dependency standard to v14.3.4
  • Schedule: ["at any time"]
  • Branch name: renovate/standard-14.x-lockfile
  • Merge into: main
  • Upgrade standard to 14.3.4
Update dependency webpack-cli to v3.3.12
  • Schedule: ["at any time"]
  • Branch name: renovate/webpack-cli-3.x-lockfile
  • Merge into: main
  • Upgrade webpack-cli to 3.3.12
Update dependency webpack-dev-server to v3.11.3
  • Schedule: ["at any time"]
  • Branch name: renovate/webpack-dev-server-3.x-lockfile
  • Merge into: main
  • Upgrade webpack-dev-server to 3.11.3
Update babel monorepo
Update dependency babel-jest to v26.6.3
  • Schedule: ["at any time"]
  • Branch name: renovate/jest-monorepo
  • Merge into: main
  • Upgrade babel-jest to 26.6.3
Update dependency babel-loader to v8.3.0
  • Schedule: ["at any time"]
  • Branch name: renovate/babel-loader-8.x-lockfile
  • Merge into: main
  • Upgrade babel-loader to 8.3.0
Update dependency webpack to v4.47.0
  • Schedule: ["at any time"]
  • Branch name: renovate/webpack-4.x-lockfile
  • Merge into: main
  • Upgrade webpack to 4.47.0
Update dependency babel-jest to v29
  • Schedule: ["at any time"]
  • Branch name: renovate/major-jest-monorepo
  • Merge into: main
  • Upgrade babel-jest to ^29.0.0
Update dependency babel-loader to v9
  • Schedule: ["at any time"]
  • Branch name: renovate/babel-loader-9.x
  • Merge into: main
  • Upgrade babel-loader to ^9.0.0
Update dependency html-webpack-plugin to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/html-webpack-plugin-5.x
  • Merge into: main
  • Upgrade html-webpack-plugin to ^5.0.0
Update dependency node-forge to v1
  • Schedule: ["at any time"]
  • Branch name: renovate/node-forge-1.x
  • Merge into: main
  • Upgrade node-forge to ^1.0.0
Update dependency standard to v17
  • Schedule: ["at any time"]
  • Branch name: renovate/standard-17.x
  • Merge into: main
  • Upgrade standard to ^17.0.0
Update dependency webpack to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/webpack-5.x
  • Merge into: main
  • Upgrade webpack to ^5.0.0
Update dependency webpack-cli to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/webpack-cli-5.x
  • Merge into: main
  • Upgrade webpack-cli to ^5.0.0
Update dependency webpack-dev-server to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/webpack-dev-server-4.x
  • Merge into: main
  • Upgrade webpack-dev-server to ^4.0.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.

@github-learning-lab
Copy link

The title of this pull request isn't what I expected!

To rename your pull request:

  1. Click on Edit next to the pull request's title.
  2. The title will turn to a text field, CI for Node in the title field.
  3. Click Save.

I'll respond when I detect this pull request has been renamed.

24 similar comments
@github-learning-lab
Copy link

The title of this pull request isn't what I expected!

To rename your pull request:

  1. Click on Edit next to the pull request's title.
  2. The title will turn to a text field, CI for Node in the title field.
  3. Click Save.

I'll respond when I detect this pull request has been renamed.

@github-learning-lab
Copy link

The title of this pull request isn't what I expected!

To rename your pull request:

  1. Click on Edit next to the pull request's title.
  2. The title will turn to a text field, CI for Node in the title field.
  3. Click Save.

I'll respond when I detect this pull request has been renamed.

@github-learning-lab
Copy link

The title of this pull request isn't what I expected!

To rename your pull request:

  1. Click on Edit next to the pull request's title.
  2. The title will turn to a text field, CI for Node in the title field.
  3. Click Save.

I'll respond when I detect this pull request has been renamed.

@github-learning-lab
Copy link

The title of this pull request isn't what I expected!

To rename your pull request:

  1. Click on Edit next to the pull request's title.
  2. The title will turn to a text field, CI for Node in the title field.
  3. Click Save.

I'll respond when I detect this pull request has been renamed.

@github-learning-lab
Copy link

The title of this pull request isn't what I expected!

To rename your pull request:

  1. Click on Edit next to the pull request's title.
  2. The title will turn to a text field, CI for Node in the title field.
  3. Click Save.

I'll respond when I detect this pull request has been renamed.

@github-learning-lab
Copy link

The title of this pull request isn't what I expected!

To rename your pull request:

  1. Click on Edit next to the pull request's title.
  2. The title will turn to a text field, CI for Node in the title field.
  3. Click Save.

I'll respond when I detect this pull request has been renamed.

@github-learning-lab
Copy link

The title of this pull request isn't what I expected!

To rename your pull request:

  1. Click on Edit next to the pull request's title.
  2. The title will turn to a text field, CI for Node in the title field.
  3. Click Save.

I'll respond when I detect this pull request has been renamed.

@github-learning-lab
Copy link

The title of this pull request isn't what I expected!

To rename your pull request:

  1. Click on Edit next to the pull request's title.
  2. The title will turn to a text field, CI for Node in the title field.
  3. Click Save.

I'll respond when I detect this pull request has been renamed.

@github-learning-lab
Copy link

The title of this pull request isn't what I expected!

To rename your pull request:

  1. Click on Edit next to the pull request's title.
  2. The title will turn to a text field, CI for Node in the title field.
  3. Click Save.

I'll respond when I detect this pull request has been renamed.

@github-learning-lab
Copy link

The title of this pull request isn't what I expected!

To rename your pull request:

  1. Click on Edit next to the pull request's title.
  2. The title will turn to a text field, CI for Node in the title field.
  3. Click Save.

I'll respond when I detect this pull request has been renamed.

@github-learning-lab
Copy link

The title of this pull request isn't what I expected!

To rename your pull request:

  1. Click on Edit next to the pull request's title.
  2. The title will turn to a text field, CI for Node in the title field.
  3. Click Save.

I'll respond when I detect this pull request has been renamed.

@github-learning-lab
Copy link

The title of this pull request isn't what I expected!

To rename your pull request:

  1. Click on Edit next to the pull request's title.
  2. The title will turn to a text field, CI for Node in the title field.
  3. Click Save.

I'll respond when I detect this pull request has been renamed.

@github-learning-lab
Copy link

The title of this pull request isn't what I expected!

To rename your pull request:

  1. Click on Edit next to the pull request's title.
  2. The title will turn to a text field, CI for Node in the title field.
  3. Click Save.

I'll respond when I detect this pull request has been renamed.

@github-learning-lab
Copy link

The title of this pull request isn't what I expected!

To rename your pull request:

  1. Click on Edit next to the pull request's title.
  2. The title will turn to a text field, CI for Node in the title field.
  3. Click Save.

I'll respond when I detect this pull request has been renamed.

@github-learning-lab
Copy link

The title of this pull request isn't what I expected!

To rename your pull request:

  1. Click on Edit next to the pull request's title.
  2. The title will turn to a text field, CI for Node in the title field.
  3. Click Save.

I'll respond when I detect this pull request has been renamed.

@github-learning-lab
Copy link

The title of this pull request isn't what I expected!

To rename your pull request:

  1. Click on Edit next to the pull request's title.
  2. The title will turn to a text field, CI for Node in the title field.
  3. Click Save.

I'll respond when I detect this pull request has been renamed.

@github-learning-lab
Copy link

The title of this pull request isn't what I expected!

To rename your pull request:

  1. Click on Edit next to the pull request's title.
  2. The title will turn to a text field, CI for Node in the title field.
  3. Click Save.

I'll respond when I detect this pull request has been renamed.

@github-learning-lab
Copy link

The title of this pull request isn't what I expected!

To rename your pull request:

  1. Click on Edit next to the pull request's title.
  2. The title will turn to a text field, CI for Node in the title field.
  3. Click Save.

I'll respond when I detect this pull request has been renamed.

@github-learning-lab
Copy link

The title of this pull request isn't what I expected!

To rename your pull request:

  1. Click on Edit next to the pull request's title.
  2. The title will turn to a text field, CI for Node in the title field.
  3. Click Save.

I'll respond when I detect this pull request has been renamed.

@github-learning-lab
Copy link

The title of this pull request isn't what I expected!

To rename your pull request:

  1. Click on Edit next to the pull request's title.
  2. The title will turn to a text field, CI for Node in the title field.
  3. Click Save.

I'll respond when I detect this pull request has been renamed.

@github-learning-lab
Copy link

The title of this pull request isn't what I expected!

To rename your pull request:

  1. Click on Edit next to the pull request's title.
  2. The title will turn to a text field, CI for Node in the title field.
  3. Click Save.

I'll respond when I detect this pull request has been renamed.

@github-learning-lab
Copy link

The title of this pull request isn't what I expected!

To rename your pull request:

  1. Click on Edit next to the pull request's title.
  2. The title will turn to a text field, CI for Node in the title field.
  3. Click Save.

I'll respond when I detect this pull request has been renamed.

@github-learning-lab
Copy link

The title of this pull request isn't what I expected!

To rename your pull request:

  1. Click on Edit next to the pull request's title.
  2. The title will turn to a text field, CI for Node in the title field.
  3. Click Save.

I'll respond when I detect this pull request has been renamed.

@github-learning-lab
Copy link

The title of this pull request isn't what I expected!

To rename your pull request:

  1. Click on Edit next to the pull request's title.
  2. The title will turn to a text field, CI for Node in the title field.
  3. Click Save.

I'll respond when I detect this pull request has been renamed.

@renovate renovate bot force-pushed the renovate/configure branch from eb71f17 to 4818a06 Compare June 26, 2022 09:16
@github-learning-lab
Copy link

The title of this pull request isn't what I expected!

To rename your pull request:

  1. Click on Edit next to the pull request's title.
  2. The title will turn to a text field, CI for Node in the title field.
  3. Click Save.

I'll respond when I detect this pull request has been renamed.

3 similar comments
@github-learning-lab
Copy link

The title of this pull request isn't what I expected!

To rename your pull request:

  1. Click on Edit next to the pull request's title.
  2. The title will turn to a text field, CI for Node in the title field.
  3. Click Save.

I'll respond when I detect this pull request has been renamed.

@github-learning-lab
Copy link

The title of this pull request isn't what I expected!

To rename your pull request:

  1. Click on Edit next to the pull request's title.
  2. The title will turn to a text field, CI for Node in the title field.
  3. Click Save.

I'll respond when I detect this pull request has been renamed.

@github-learning-lab
Copy link

The title of this pull request isn't what I expected!

To rename your pull request:

  1. Click on Edit next to the pull request's title.
  2. The title will turn to a text field, CI for Node in the title field.
  3. Click Save.

I'll respond when I detect this pull request has been renamed.

@github-learning-lab
Copy link

The title of this pull request isn't what I expected!

To rename your pull request:

  1. Click on Edit next to the pull request's title.
  2. The title will turn to a text field, CI for Node in the title field.
  3. Click Save.

I'll respond when I detect this pull request has been renamed.

8 similar comments
@github-learning-lab
Copy link

The title of this pull request isn't what I expected!

To rename your pull request:

  1. Click on Edit next to the pull request's title.
  2. The title will turn to a text field, CI for Node in the title field.
  3. Click Save.

I'll respond when I detect this pull request has been renamed.

@github-learning-lab
Copy link

The title of this pull request isn't what I expected!

To rename your pull request:

  1. Click on Edit next to the pull request's title.
  2. The title will turn to a text field, CI for Node in the title field.
  3. Click Save.

I'll respond when I detect this pull request has been renamed.

@github-learning-lab
Copy link

The title of this pull request isn't what I expected!

To rename your pull request:

  1. Click on Edit next to the pull request's title.
  2. The title will turn to a text field, CI for Node in the title field.
  3. Click Save.

I'll respond when I detect this pull request has been renamed.

@github-learning-lab
Copy link

The title of this pull request isn't what I expected!

To rename your pull request:

  1. Click on Edit next to the pull request's title.
  2. The title will turn to a text field, CI for Node in the title field.
  3. Click Save.

I'll respond when I detect this pull request has been renamed.

@github-learning-lab
Copy link

The title of this pull request isn't what I expected!

To rename your pull request:

  1. Click on Edit next to the pull request's title.
  2. The title will turn to a text field, CI for Node in the title field.
  3. Click Save.

I'll respond when I detect this pull request has been renamed.

@github-learning-lab
Copy link

The title of this pull request isn't what I expected!

To rename your pull request:

  1. Click on Edit next to the pull request's title.
  2. The title will turn to a text field, CI for Node in the title field.
  3. Click Save.

I'll respond when I detect this pull request has been renamed.

@github-learning-lab
Copy link

The title of this pull request isn't what I expected!

To rename your pull request:

  1. Click on Edit next to the pull request's title.
  2. The title will turn to a text field, CI for Node in the title field.
  3. Click Save.

I'll respond when I detect this pull request has been renamed.

@github-learning-lab
Copy link

The title of this pull request isn't what I expected!

To rename your pull request:

  1. Click on Edit next to the pull request's title.
  2. The title will turn to a text field, CI for Node in the title field.
  3. Click Save.

I'll respond when I detect this pull request has been renamed.

@renovate renovate bot force-pushed the renovate/configure branch from 4818a06 to 188e018 Compare December 15, 2023 02:18
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.

0 participants