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

Merged
merged 1 commit into from Jun 14, 2022
Merged

Configure Renovate #37

merged 1 commit into from Jun 14, 2022

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 8, 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
  • Enable Renovate Dependency Dashboard creation
  • If semantic commits detected, use semantic commit type fix for dependencies and chore for all others
  • 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 10 open PRs at any time
  • Group known monorepo packages together
  • Use curated list of recommended non-monorepo package groupings
  • Fix some problems with very old Maven commons versions
  • Ignore spring cloud 1.x releases
  • Ignore web3j 5.0.0 release
  • Ignore http4s digest-based 1.x milestones
  • Use node versioning for @types/node
  • Limit concurrent requests to reduce load on Repology servers until we can fix this properly, see issue 10133
  • Do not upgrade from Alpine stable to edge
  • 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:

chore(deps): update dependency autoprefixer to v10.4.7
  • Schedule: ["before 3am on Monday"]
  • Branch name: renovate/autoprefixer-10.x-lockfile
  • Merge into: main
  • Upgrade autoprefixer to 10.4.7
chore(deps): update dependency postcss to v8.4.14
  • Schedule: ["before 3am on Monday"]
  • Branch name: renovate/postcss-8.x-lockfile
  • Merge into: main
  • Upgrade postcss to 8.4.14
chore(deps): update dependency eslint-config-next to v12.1.6
  • Schedule: ["before 3am on Monday"]
  • Branch name: renovate/nextjs-monorepo
  • Merge into: main
  • Upgrade eslint-config-next to 12.1.6
chore(deps): update dependency eslint-config-prettier to v8.5.0
  • Schedule: ["before 3am on Monday"]
  • Branch name: renovate/eslint-config-prettier-8.x-lockfile
  • Merge into: main
  • Upgrade eslint-config-prettier to 8.5.0
fix(deps): update dependency prismjs to v1.27.0 [security]
  • Branch name: renovate/npm-prismjs-vulnerability
  • Merge into: main
  • Upgrade prismjs to 1.27.0
fix(deps): update dependency @​tailwindcss/typography to v0.5.2
  • Schedule: ["before 3am on Monday"]
  • Branch name: renovate/tailwindcss-typography-0.x-lockfile
  • Merge into: main
  • Upgrade @tailwindcss/typography to 0.5.2
chore(deps): update dependency tailwindcss to v3.1.2
  • Schedule: ["before 3am on Monday"]
  • Branch name: renovate/tailwindcss-3.x-lockfile
  • Merge into: main
  • Upgrade tailwindcss to 3.1.2
fix(deps): update dependency @​netlify/plugin-nextjs to 4.9
chore(deps): update dependency eslint to v8
  • Schedule: ["before 3am on Monday"]
  • Branch name: renovate/eslint-8.x
  • Merge into: main
  • Upgrade eslint to <9.0.0
fix(deps): update dependency next-mdx-remote to v4
  • Schedule: ["before 3am on Monday"]
  • Branch name: renovate/next-mdx-remote-4.x
  • Merge into: main
  • Upgrade next-mdx-remote to ^4.0.0
fix(deps): update react monorepo to v18 (major)
  • Schedule: ["before 3am on Monday"]
  • Branch name: renovate/major-react-monorepo
  • Merge into: main
  • Upgrade react to ^18.0.0
  • Upgrade react-dom to ^18.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 Mend Renovate. View repository job log here.

@netlify
Copy link

netlify bot commented Jun 8, 2022

Deploy Preview for bejamas-nextjs-blog ready!

Name Link
🔨 Latest commit 1816333
🔍 Latest deploy log https://app.netlify.com/sites/bejamas-nextjs-blog/deploys/62a8b3efb7db4a0008dee852
😎 Deploy Preview https://deploy-preview-37--bejamas-nextjs-blog.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

@maxcell maxcell merged commit 3de8e13 into main Jun 14, 2022
@maxcell maxcell deleted the renovate/configure branch June 14, 2022 21:41
Lysak pushed a commit to Lysak/blog-web that referenced this pull request Sep 26, 2022
Co-authored-by: Renovate Bot <bot@renovateapp.com>
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

2 participants