2
7
Fork
You've already forked webidamd
1

Configure Renovate #15

Merged
_renovate merged 1 commit from renovate/configure into master 2022年05月02日 23:41:38 +02:00
_renovate commented 2022年05月02日 17:31:54 +02:00 (Migrated from edugit.org)
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

  • Cargo.toml (cargo)
  • .gitlab-ci.yml (gitlabci)

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

With your current configuration, Renovate will create 12 Merge Requests:

Update Rust crate libc to ^0.2.125
  • Schedule: ["at any time"]
  • Branch name: renovate/libc-0.x
  • Merge into: master
  • Upgrade libc to ^0.2.125
Update Rust crate log to ^0.4.16
  • Schedule: ["at any time"]
  • Branch name: renovate/log-0.x
  • Merge into: master
  • Upgrade log to ^0.4.16
Update Rust crate reqwest to ^0.11.10
  • Schedule: ["at any time"]
  • Branch name: renovate/reqwest-0.x
  • Merge into: master
  • Upgrade reqwest to ^0.11.10
Update Rust crate serde to ^1.0.137
  • Schedule: ["at any time"]
  • Branch name: renovate/serde-1.x
  • Merge into: master
  • Upgrade serde to ^1.0.137
Update Rust crate serde_json to ^1.0.80
  • Schedule: ["at any time"]
  • Branch name: renovate/serde_json-1.x
  • Merge into: master
  • Upgrade serde_json to ^1.0.80
Update Rust crate config to ^0.13.1
  • Schedule: ["at any time"]
  • Branch name: renovate/config-0.x
  • Merge into: master
  • Upgrade config to ^0.13.1
Update Rust crate lazy_static to ^1.4.0
  • Schedule: ["at any time"]
  • Branch name: renovate/lazy_static-1.x
  • Merge into: master
  • Upgrade lazy_static to ^1.4.0
Update Rust crate oauth2 to ^4.2.0
  • Schedule: ["at any time"]
  • Branch name: renovate/oauth2-4.x
  • Merge into: master
  • Upgrade oauth2 to ^4.2.0
Update Rust crate pamsm to ^0.5.2
  • Schedule: ["at any time"]
  • Branch name: renovate/pamsm-0.x
  • Merge into: master
  • Upgrade pamsm to ^0.5.2
Update Rust crate xdg to ^2.4.1
  • Schedule: ["at any time"]
  • Branch name: renovate/xdg-2.x
  • Merge into: master
  • Upgrade xdg to ^2.4.1
Update Rust crate paste to v1
  • Schedule: ["at any time"]
  • Branch name: renovate/paste-1.x
  • Merge into: master
  • Upgrade paste to ^1.0
Update Rust crate syslog to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/syslog-6.x
  • Merge into: master
  • Upgrade syslog to ^6.0.1

🚸 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 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 * `Cargo.toml` (cargo) * `.gitlab-ci.yml` (gitlabci) ### 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 With your current configuration, Renovate will create 12 Merge Requests: <details> <summary>Update Rust crate libc to ^0.2.125</summary> - Schedule: ["at any time"] - Branch name: `renovate/libc-0.x` - Merge into: `master` - Upgrade libc to `^0.2.125` </details> <details> <summary>Update Rust crate log to ^0.4.16</summary> - Schedule: ["at any time"] - Branch name: `renovate/log-0.x` - Merge into: `master` - Upgrade log to `^0.4.16` </details> <details> <summary>Update Rust crate reqwest to ^0.11.10</summary> - Schedule: ["at any time"] - Branch name: `renovate/reqwest-0.x` - Merge into: `master` - Upgrade reqwest to `^0.11.10` </details> <details> <summary>Update Rust crate serde to ^1.0.137</summary> - Schedule: ["at any time"] - Branch name: `renovate/serde-1.x` - Merge into: `master` - Upgrade serde to `^1.0.137` </details> <details> <summary>Update Rust crate serde_json to ^1.0.80</summary> - Schedule: ["at any time"] - Branch name: `renovate/serde_json-1.x` - Merge into: `master` - Upgrade serde_json to `^1.0.80` </details> <details> <summary>Update Rust crate config to ^0.13.1</summary> - Schedule: ["at any time"] - Branch name: `renovate/config-0.x` - Merge into: `master` - Upgrade config to `^0.13.1` </details> <details> <summary>Update Rust crate lazy_static to ^1.4.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/lazy_static-1.x` - Merge into: `master` - Upgrade lazy_static to `^1.4.0` </details> <details> <summary>Update Rust crate oauth2 to ^4.2.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/oauth2-4.x` - Merge into: `master` - Upgrade oauth2 to `^4.2.0` </details> <details> <summary>Update Rust crate pamsm to ^0.5.2</summary> - Schedule: ["at any time"] - Branch name: `renovate/pamsm-0.x` - Merge into: `master` - Upgrade pamsm to `^0.5.2` </details> <details> <summary>Update Rust crate xdg to ^2.4.1</summary> - Schedule: ["at any time"] - Branch name: `renovate/xdg-2.x` - Merge into: `master` - Upgrade xdg to `^2.4.1` </details> <details> <summary>Update Rust crate paste to v1</summary> - Schedule: ["at any time"] - Branch name: `renovate/paste-1.x` - Merge into: `master` - Upgrade paste to `^1.0` </details> <details> <summary>Update Rust crate syslog to v6</summary> - Schedule: ["at any time"] - Branch name: `renovate/syslog-6.x` - Merge into: `master` - Upgrade syslog to `^6.0.1` </details> <br /> 🚸 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](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).
_renovate commented 2022年05月02日 23:31:53 +02:00 (Migrated from edugit.org)
Copy link

added 2 commits

Compare with previous version

added 2 commits <ul><li>0e4237ee - 1 commit from branch <code>master</code></li><li>d0d72e8b - Add renovate.json</li></ul> [Compare with previous version](/AlekSIS/libs/system-auth-webapi/-/merge_requests/3/diffs?diff_id=20797&start_sha=2cd373ab09c19f173053e8221a1cc000f9420895)
nik commented 2022年05月02日 23:41:38 +02:00 (Migrated from edugit.org)
Copy link

mentioned in commit ba75dfac4c

mentioned in commit ba75dfac4cd50d043192c24385b7c0645a0aa945
Sign in to join this conversation.
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Bergblau/webidamd!15
Reference in a new issue
Bergblau/webidamd
No description provided.
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?