erichardson/py-eagle-mqtt
1
0
Fork 0
Code Issues 1 Pull Requests 5 Actions Packages Projects Releases 11 Wiki Activity

Configure Renovate #6

Merged
erichardson merged 0 commits from renovate/configure into master 2021-12-02 04:53:55 +00:00
Conversation 3 Commits - Files Changed -
erichardson commented 2021-12-02 04:48:59 +00:00 (Migrated from gitlab.evanshome.io)
Copy Link

Welcome to Renovate! This is an onboarding MR to help you understand and configure settings before regular Merge Requests begin.

🚦 To activate Renovate, merge this Merge Request. To disable Renovate, simply close this Merge Request unmerged.

Detected Package Files

  • Docker/requirements.txt (pip_requirements)

Configuration Summary

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

  • Start dependency updates only once this onboarding MR 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 MR creation to a maximum of two per hour
  • Limit to maximum 20 open MRs 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 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

🔡 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 Merge Requests in the "What to Expect" section below will be updated the next time Renovate runs.

What to Expect

It looks like your repository dependencies are already up-to-date and no Merge Requests will be necessary right away.

❓ 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 MR has been generated by Renovate Bot.

Welcome to [Renovate](https://github.com/renovatebot/renovate)! This is an onboarding MR to help you understand and configure settings before regular Merge Requests begin. 🚦 To activate Renovate, merge this Merge Request. To disable Renovate, simply close this Merge Request unmerged. --- ### Detected Package Files * `Docker/requirements.txt` (pip_requirements) ### Configuration Summary Based on the default config's presets, Renovate will: - Start dependency updates only once this onboarding MR is merged - Enable Renovate Dependency Dashboard creation - If semantic commits detected, use semantic commit type <code>fix</code> for dependencies and <code>chore</code> for all others - Ignore `node_modules`, `bower_components`, `vendor` and various test/tests directories - Autodetect whether to pin dependencies or maintain ranges - Rate limit MR creation to a maximum of two per hour - Limit to maximum 20 open MRs 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 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 🔡 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 Merge Requests in the "What to Expect" section below will be updated the next time Renovate runs. --- ### What to Expect It looks like your repository dependencies are already up-to-date and no Merge Requests will be necessary right away. --- ❓ 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 MR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).
erichardson commented 2021-12-02 04:53:49 +00:00 (Migrated from gitlab.evanshome.io)
Copy Link

approved this merge request

By Evan Richardson on 2021-12-02T04:53:49 (imported from GitLab)

approved this merge request *By Evan Richardson on 2021-12-02T04:53:49 (imported from GitLab)*
erichardson commented 2021-12-02 04:53:55 +00:00 (Migrated from gitlab.evanshome.io)
Copy Link

mentioned in commit 8d2db8617d

By Evan Richardson on 2021-12-02T04:53:55 (imported from GitLab)

mentioned in commit 8d2db8617dd0f2e29c741df491b0a00e07d3cd3f *By Evan Richardson on 2021-12-02T04:53:55 (imported from GitLab)*
erichardson (Migrated from gitlab.evanshome.io) approved these changes 2024-02-04 00:35:55 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
erichardson
Labels
Clear labels
bot
upgrade
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
gitea-service-account renovate erichardson
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: erichardson/py-eagle-mqtt#6
Delete Branch "renovate/configure"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?