Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Configure Renovate #13

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

Closed
renovate wants to merge 1 commit into main from renovate/configure
Closed

Configure Renovate #13

renovate wants to merge 1 commit into main from renovate/configure

Conversation

@renovate
Copy link

@renovate renovate bot commented Mar 22, 2021

WhiteSource 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
  • 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)
  • 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
  • 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
  • Ignore spring cloud 1.x releases
  • Ignore http4s digest-based 1.x milestones
  • Weekly schedule on early monday mornings
  • Run Renovate on following schedule: before 3am on Monday

🔡 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.


What to Expect

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

Update dependency elliptic to 6.5.4 [SECURITY]
  • Branch name: renovate/npm-elliptic-vulnerability
  • Merge into: main
  • Upgrade elliptic to 6.5.4
Update dependency ini to 1.3.6 [SECURITY]
  • Branch name: renovate/npm-ini-vulnerability
  • Merge into: main
  • Upgrade ini to 1.3.6
Update dependency node-fetch to 2.6.1 [SECURITY]
  • Branch name: renovate/npm-node-fetch-vulnerability
  • Merge into: main
  • Upgrade node-fetch to 2.6.1
Update dependency object-path to 0.11.5 [SECURITY]
  • Branch name: renovate/npm-object-path-vulnerability
  • Merge into: main
  • Upgrade object-path to 0.11.5
Update dependency ssri to 8.0.1 [SECURITY]
  • Branch name: renovate/npm-ssri-vulnerability
  • Merge into: main
  • Upgrade ssri to 8.0.1
Update dependency next to v9.5.5
  • Schedule: ["before 3am on Monday"]
  • Branch name: renovate/nextjs-monorepo
  • Merge into: main
  • Upgrade next to 9.5.5
Update dependency next-on-netlify to v2.9.0
  • Schedule: ["before 3am on Monday"]
  • Branch name: renovate/next-on-netlify-2.x-lockfile
  • Merge into: main
  • Upgrade next-on-netlify to 2.9.0
Update react monorepo to v16.14.0
  • Schedule: ["before 3am on Monday"]
  • Branch name: renovate/react-monorepo
  • Merge into: main
  • Upgrade react to 16.14.0
  • Upgrade react-dom to 16.14.0
Update dependency next to v10
  • Schedule: ["before 3am on Monday"]
  • Branch name: renovate/major-nextjs-monorepo
  • Merge into: main
  • Upgrade next to ^10.0.0
Update react monorepo to v17 (major)
  • Schedule: ["before 3am on Monday"]
  • Branch name: renovate/major-react-monorepo
  • Merge into: main
  • Upgrade react to ^17.0.0
  • Upgrade react-dom to ^17.0.0
Lock file maintenance
  • Schedule: ["before 5am on monday"]
  • Branch name: renovate/lock-file-maintenance
  • Merge into: main
  • Regenerate lock files to use latest dependency versions

🚸 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 WhiteSource Renovate. View repository job log here.

@rybit rybit closed this Mar 22, 2021
@rybit rybit deleted the renovate/configure branch March 22, 2021 20:44
Copy link
Author

renovate bot commented Mar 22, 2021
edited
Loading

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

AltStyle によって変換されたページ (->オリジナル) /