Configure Renovate #5

Merged
inhji merged 1 commits from renovate/configure into main 2023-03-18 08:13:07 +01:00
Owner

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

  • .tool-versions (asdf)
  • mix.exs (mix)

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 Renovate detects semantic commits, it will use semantic commit type fix for dependencies and chore for all others.
  • 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.
  • apollo-server packages became scoped.
  • babel-eslint was renamed under the @babel scope.
  • Replace containerbase dependencies.
  • cucumber became scoped.
  • fastify packages became scoped.
  • hapi became scoped.
  • Jade was renamed to Pug.
  • joi became scoped under the hapi organization.
  • joi was moved out of the hapi organization.
  • The Kubernetes container registry has changed from k8s.gcr.io to registry.k8s.io.
  • The Kubernetes container registry has changed from k8s.gcr.io to registry.k8s.io.
  • The material-ui monorepo org was renamed from @material-ui to @mui.
  • The messageformat monorepo package naming scheme changed from messageFormat-{{package}}-to-@messageformat/{{package}}.
  • middie became scoped.
  • now was renamed to vercel.
  • @parcel/css was renamed to lightningcss.
  • react-query/devtools became scoped under the tanstack organization.
  • react-query became scoped under the tanstack organization.
  • react-scripts supports TypeScript since version 2.1.0.
  • The @renovate/pep440 package was renamed to @renovatebot/pep440.
  • The node-resolve plugin for rollup became scoped.
  • The vso-task-lib package is now published as azure-pipelines-task-lib.
  • The vsts-task-lib package is now published as azure-pipelines-task-lib.
  • The xmldom package is now published as @xmldom/xmldom.
  • A collection of workarounds for known problems with packages.

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

Update dependency elixir to v1.14.3
  • Schedule: ["at any time"]
  • Branch name: renovate/elixir-1.x
  • Merge into: main
  • Upgrade elixir to 1.14.3
Update dependency esbuild to ~> 0.7
  • Schedule: ["at any time"]
  • Branch name: renovate/esbuild-0.x
  • Merge into: main
  • Upgrade esbuild to ~> 0.7
Update dependency finch to ~> 0.15
  • Schedule: ["at any time"]
  • Branch name: renovate/finch-0.x
  • Merge into: main
  • Upgrade finch to ~> 0.15
Update dependency gettext to ~> 0.22
  • Schedule: ["at any time"]
  • Branch name: renovate/gettext-0.x
  • Merge into: main
  • Upgrade gettext to ~> 0.22
Update dependency tailwind to ~> 0.2.0
  • Schedule: ["at any time"]
  • Branch name: renovate/tailwind-0.x
  • Merge into: main
  • Upgrade tailwind to ~> 0.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 Renovate Bot.

Welcome to [Renovate](https://github.com/renovatebot/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 * `.tool-versions` (asdf) * `mix.exs` (mix) ### 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 Renovate detects semantic commits, it will use semantic commit type `fix` for dependencies and `chore` for all others. - 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. - `apollo-server` packages became scoped. - `babel-eslint` was renamed under the `@babel` scope. - Replace containerbase dependencies. - `cucumber` became scoped. - `fastify` packages became scoped. - `hapi` became scoped. - Jade was renamed to Pug. - `joi` became scoped under the `hapi` organization. - `joi` was moved out of the `hapi` organization. - The Kubernetes container registry has changed from `k8s.gcr.io` to `registry.k8s.io`. - The Kubernetes container registry has changed from `k8s.gcr.io` to `registry.k8s.io`. - The `material-ui` monorepo org was renamed from `@material-ui` to `@mui`. - The `messageformat` monorepo package naming scheme changed from `messageFormat-{{package}}`-to-`@messageformat/{{package}}`. - `middie` became scoped. - `now` was renamed to `vercel`. - `@parcel/css` was renamed to `lightningcss`. - `react-query/devtools` became scoped under the `tanstack` organization. - `react-query` became scoped under the `tanstack` organization. - `react-scripts` supports TypeScript since version `2.1.0`. - The `@renovate/pep440` package was renamed to `@renovatebot/pep440`. - The node-resolve plugin for rollup became scoped. - The `vso-task-lib` package is now published as `azure-pipelines-task-lib`. - The `vsts-task-lib` package is now published as `azure-pipelines-task-lib`. - The `xmldom` package is now published as `@xmldom/xmldom`. - A collection of workarounds for known problems with packages. 🔡 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 5 Pull Requests: <details> <summary>Update dependency elixir to v1.14.3</summary> - Schedule: ["at any time"] - Branch name: `renovate/elixir-1.x` - Merge into: `main` - Upgrade [elixir](https://github.com/elixir-lang/elixir) to `1.14.3` </details> <details> <summary>Update dependency esbuild to ~> 0.7</summary> - Schedule: ["at any time"] - Branch name: `renovate/esbuild-0.x` - Merge into: `main` - Upgrade esbuild to `~> 0.7` </details> <details> <summary>Update dependency finch to ~> 0.15</summary> - Schedule: ["at any time"] - Branch name: `renovate/finch-0.x` - Merge into: `main` - Upgrade finch to `~> 0.15` </details> <details> <summary>Update dependency gettext to ~> 0.22</summary> - Schedule: ["at any time"] - Branch name: `renovate/gettext-0.x` - Merge into: `main` - Upgrade gettext to `~> 0.22` </details> <details> <summary>Update dependency tailwind to ~> 0.2.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/tailwind-0.x` - Merge into: `main` - Upgrade tailwind to `~> 0.2.0` </details> <br /> 🚸 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](https://docs.renovatebot.com/), particularly the Getting Started section. If you need any further assistance then you can also [request help here](https://github.com/renovatebot/renovate/discussions). --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).
inhji added 1 commit 2023-03-18 08:12:06 +01:00
inhji merged commit b67e6daf58 into main 2023-03-18 08:13:07 +01:00
Sign in to join this conversation.
No reviewers
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: inhji/chiya#5
No description provided.