cinder/vscode-cinder
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Configure Renovate #1

Merged
jimsy merged 1 commit from renovate/configure into main 2023-02-17 17:47:52 +13:00
Conversation 2 Commits 1 Files changed 1 +5
jimsy commented 2023-02-17 17:47:21 +13:00 (Migrated from gitlab.com)
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

  • package.json (npm)

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 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.
  • Automatically detect the best rangeStrategy to use.
  • Rate limit MR creation to a maximum of two per hour.
  • Limit to maximum 10 open MRs at any time.
  • Group known monorepo packages together.
  • Use curated list of recommended non-monorepo package groupings.
  • A collection of workarounds for known problems with packages.
  • Use semantic prefixes for commit messages and MR titles.
  • Use chore as semantic commit type for commit messages and MR titles.
  • Removes rate limit for MR creation per hour.
  • Remove limit for open MRs at any time.
  • Automerge all upgrades (including major) if they pass tests.
  • Assign MRs to jimsy.
  • Rebase existing MRs any time the base branch has been updated.
  • Raise MR when vulnerability alerts are detected.
  • Disable Renovate Dependency Dashboard creation.

🔡 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 1 Merge Request:

chore(deps): lock file maintenance
  • Branch name: renovate/lock-file-maintenance
  • Merge into: main
  • Regenerate lock files to use latest dependency versions

❓ 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 * `package.json` (npm) ### 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 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. - Automatically detect the best rangeStrategy to use. - Rate limit MR creation to a maximum of two per hour. - Limit to maximum 10 open MRs at any time. - Group known monorepo packages together. - Use curated list of recommended non-monorepo package groupings. - A collection of workarounds for known problems with packages. - Use semantic prefixes for commit messages and MR titles. - Use `chore` as semantic commit type for commit messages and MR titles. - Removes rate limit for MR creation per hour. - Remove limit for open MRs at any time. - Automerge all upgrades (including `major`) if they pass tests. - Assign MRs to `jimsy`. - Rebase existing MRs any time the base branch has been updated. - Raise MR when vulnerability alerts are detected. - Disable Renovate Dependency Dashboard creation. 🔡 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 1 Merge Request: <details> <summary>chore(deps): lock file maintenance</summary> - Branch name: `renovate/lock-file-maintenance` - Merge into: `main` - Regenerate lock files to use latest dependency versions </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).
jimsy commented 2023-02-17 17:47:23 +13:00 (Migrated from gitlab.com)
Copy link

assigned to @jimsy

assigned to @jimsy
jimsy commented 2023-02-17 17:47:52 +13:00 (Migrated from gitlab.com)
Copy link

mentioned in commit 21a0d9222d

mentioned in commit 21a0d9222d4c81d1e6eb3030accc5d68975402bd
Sign in to join this conversation.
Reviewers
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: cinder/vscode-cinder#1
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?