Renovate/renovate-runner
2
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

Configure Renovate #1

Merged
jank merged 1 commits from renovate/configure into main 2024-07-12 05:22:14 +00:00
Conversation 0 Commits 1 Files Changed 1 +6
Renovate commented 2024-07-12 05:21:26 +00:00
Owner
Copy Link

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

  • .gitea/workflows/renovate.yaml (github-actions)

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.
  • 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 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.
  • Preserve (but continue to upgrade) any existing SemVer ranges.
  • Enable Renovate Dependency Dashboard creation.
  • Rebase existing PRs any time the base branch has been updated.
  • Raise PR when vulnerability alerts are detected with label 'security'.
  • Use curated list of recommended non-monorepo package groupings.
  • Show all Merge Confidence badges for pull requests.

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

Update ghcr.io/renovatebot/renovate Docker tag to v37.429.0
  • Schedule: ["at any time"]
  • Branch name: renovate/ghcr.io-renovatebot-renovate-37.x
  • Merge into: main
  • Upgrade ghcr.io/renovatebot/renovate to 37.429.0

❓ 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 * `.gitea/workflows/renovate.yaml` (github-actions) ### 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. - 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 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. - Preserve (but continue to upgrade) any existing SemVer ranges. - Enable Renovate Dependency Dashboard creation. - Rebase existing PRs any time the base branch has been updated. - Raise PR when vulnerability alerts are detected with label `'security'`. - Use curated list of recommended non-monorepo package groupings. - Show all Merge Confidence badges for pull requests. 🔡 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 1 Pull Request: <details> <summary>Update ghcr.io/renovatebot/renovate Docker tag to v37.429.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/ghcr.io-renovatebot-renovate-37.x` - Merge into: `main` - Upgrade [ghcr.io/renovatebot/renovate](https://github.com/renovatebot/renovate) to `37.429.0` </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). <!--renovate-config-hash:0a0b8841b14278c0c061ba4db2615c8f351f5dda327a6ee5707d6e1ee5980f1c-->
Renovate added 1 commit 2024-07-12 05:21:26 +00:00
jank merged commit d0d9939b3a into main 2024-07-12 05:22:14 +00:00
jank deleted branch renovate/configure 2024-07-12 05:22:14 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
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.

Dependencies

No dependencies set.

Reference: Renovate/renovate-runner#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?