[PR #39] [MERGED] Configure Renovate #117

New issue

Closed

opened 2026-03-03 14:29:44 +03:00 by kerem · 0 comments

kerem commented

2026-03-03 14:29:44 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/konstruktoid/hardening/pull/39
Author: @renovate[bot]
Created: 1/8/2019
Status: ✅ Merged
Merged: 1/8/2019
Merged by: @konstruktoid

Base: master ← Head: renovate/configure

📝 Commits (1)

5c7a8c6 Add renovate.json

📊 Changes

1 file changed (+5 additions, -0 deletions)

View changed files

➕ renovate.json (+5 -0)

📄 Description

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

action-shellcheck/Dockerfile (dockerfile)

Configuration Summary

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

Start dependency updates only once this Configure Renovate PR is merged
Separate major versions of dependencies into individual branches/PRs
Do not separate patch and minor upgrades into separate PRs for the same dependency
Upgrade to unstable versions only if the existing version is unstable
Raise PRs immediately (after branch is created)
Use renovate/ as prefix for all branch names
If semantic commits detected, use semantic commit type fix for dependencies and chore for all others
Keep existing branches updated even when not scheduled
Disable automerging feature - wait for humans to merge all PRs
Ignore node_modules, bower_components, vendor and various test/tests directories
Update existing lock files only when package.json is modified
Autodetect whether to pin dependencies or maintain ranges
Rate limit PR creation to a maximum of two per hour
Limit to maximum 20 concurrent Renovate PRs at any time
Group known monorepo packages together
Use curated list of recommended non-monorepo package groupings

🔡 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

It looks like your repository dependencies are already up-to-date and no Pull 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 PR has been generated by Renovate Bot. View repository job log here.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/konstruktoid/hardening/pull/39 **Author:** [@renovate[bot]](https://github.com/apps/renovate) **Created:** 1/8/2019 **Status:** ✅ Merged **Merged:** 1/8/2019 **Merged by:** [@konstruktoid](https://github.com/konstruktoid) **Base:** `master` ← **Head:** `renovate/configure` --- ### 📝 Commits (1) - [`5c7a8c6`](https://github.com/konstruktoid/hardening/commit/5c7a8c6720cd2f09e96e60ef84dce099b0869e8e) Add renovate.json ### 📊 Changes **1 file changed** (+5 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `renovate.json` (+5 -0) </details> ### 📄 Description Welcome to [Renovate](https://renovatebot.com)! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin. :vertical_traffic_light: To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged. --- ### Detected Package Files * `action-shellcheck/Dockerfile` (dockerfile) ### Configuration Summary Based on the default config's presets, Renovate will: - Start dependency updates only once this Configure Renovate PR is merged - Separate major versions of dependencies into individual branches/PRs - Do not separate patch and minor upgrades into separate PRs for the same dependency - Upgrade to unstable versions only if the existing version is unstable - Raise PRs immediately (after branch is created) - Use <code>renovate/</code> as prefix for all branch names - If semantic commits detected, use semantic commit type <code>fix</code> for dependencies and <code>chore</code> for all others - Keep existing branches updated even when not scheduled - Disable automerging feature - wait for humans to merge all PRs - Ignore `node_modules`, `bower_components`, `vendor` and various test/tests directories - Update existing lock files only when <code>package.json</code> is modified - Autodetect whether to pin dependencies or maintain ranges - Rate limit PR creation to a maximum of two per hour - Limit to maximum 20 concurrent Renovate PRs at any time - Group known monorepo packages together - Use curated list of recommended non-monorepo package groupings :abcd: 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 It looks like your repository dependencies are already up-to-date and no Pull Requests will be necessary right away. --- :question: Got questions? Check out Renovate's [Docs](https://renovatebot.com/docs/), particularly the Getting Started section. If you need any further assistance then you can also [request help here](https://togithub.com/renovatebot/config-help/issues). --- This PR has been generated by [Renovate Bot](https://togithub.com/marketplace/renovate). View repository job log [here](https://renovatebot.com/dashboard#konstruktoid/hardening). --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>