unboundsoftware/release-test
6
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases 17 Activity

chore: Configure Renovate #4

Merged
group_2759636_bot_1c34751f7eccad09e089ac15ee7bd902 merged 1 commits from renovate/configure into main 2024-10-03 06:43:27 +00:00
Conversation 1 Commits 1 Files Changed 1
+6
group_2759636_bot_1c34751f7eccad09e089ac15ee7bd902 commented 2024-10-02 07:51:15 +00:00 (Migrated from gitlab.com)
Copy Link
Copy Source

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

  • .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
  • Use semantic prefixes for commit messages and MR titles.
  • Enable Renovate Dependency Dashboard creation.
  • Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
  • Ignore node_modules, bower_components, vendor and various test/tests (except for nuget) directories.
  • Group known monorepo packages together.
  • Use curated list of recommended non-monorepo package groupings.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Merge Request description the next time it 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 * `.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 - Use semantic prefixes for commit messages and MR titles. - Enable Renovate Dependency Dashboard creation. - Use semantic commit type `fix` for dependencies and `chore` for all others if semantic commits are in use. - Ignore `node_modules`, `bower_components`, `vendor` and various test/tests (except for nuget) directories. - Group known monorepo packages together. - Use curated list of recommended non-monorepo package groupings. - Apply crowd-sourced package replacement rules. - Apply crowd-sourced workarounds for known problems with packages. 🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to `renovate.json` in this branch. Renovate will update the Merge Request description the next time it 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). <!--renovate-config-hash:e80b4e42a3043bc12fa0640db4bac392d2bf770acf841360d7c8ceeeac2ec1a9-->
argoyle commented 2024-10-03 06:43:17 +00:00 (Migrated from gitlab.com)
Copy Link
Copy Source

added 3 commits

  • 2d06f9be...1fefccde - 2 commits from branch main
  • 0ad731aa - Add renovate.json

Compare with previous version

added 3 commits <ul><li>2d06f9be...1fefccde - 2 commits from branch <code>main</code></li><li>0ad731aa - Add renovate.json</li></ul> [Compare with previous version](/unboundsoftware/release-test/-/merge_requests/3/diffs?diff_id=1138439233&start_sha=2d06f9be7ccf6720fa6f4ca0cab825ef49c60850)
argoyle (Migrated from gitlab.com) merged commit into main 2024-10-03 06:43:28 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
acctest (Shiny Acctest) argoyle (Joakim Olsson) buildtools (Buildtools) kubernetes (Kubernetes) releaser (Unbound Releaser) renovate (Renovate Bot)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: unboundsoftware/release-test#4
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?