privilegedescalation/org
12
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

chore: Configure Renovate #64

Merged
privilegedescalation-engineer[bot] merged 1 commits from renovate/configure into main 2026-05-20 03:03:46 +00:00
Conversation 0 Commits 1 Files Changed 1
+6
privilegedescalation-engineer[bot] commented 2026-05-13 17:34:38 +00:00 (Migrated from github.com)
Copy Link
Copy Source

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

  • .github/workflows/ci.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 (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.
  • 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.
  • Run Renovate on following schedule: every weekend

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Pull Request description the next time it runs.

You have configured Renovate to use branch main as base branch.

What to Expect

With your current configuration, Renovate will create 2 Pull Requests:

chore(deps): pin dependencies
chore(deps): update github-actions major updates (major)
  • Schedule: ["every weekend"]
  • Branch name: renovate/major-github-actions-major-updates
  • Merge into: main
  • Upgrade DavidAnson/markdownlint-cli2-action to ded1f9488f68a970bc66ea5619e13e9b52e601cd
  • Upgrade actions/checkout to de0fac2e4500dabe0009e67214ff5f5447ce83dd

❓ 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://redirect.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 * `.github/workflows/ci.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 (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. - 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. - Run Renovate on following schedule: every weekend 🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to `renovate.json` in this branch. Renovate will update the Pull Request description the next time it runs. --- You have configured Renovate to use branch `main` as base branch. ### What to Expect With your current configuration, Renovate will create 2 Pull Requests: <details> <summary>chore(deps): pin dependencies</summary> - Schedule: ["every weekend"] - Branch name: `renovate/pin-dependencies` - Merge into: `main` - Upgrade [DavidAnson/markdownlint-cli2-action](https://redirect.github.com/DavidAnson/markdownlint-cli2-action) to `05f32210e84442804257b2a6f20b273450ec8265` - Upgrade [actions/checkout](https://redirect.github.com/actions/checkout) to `34e114876b0b11c390a56381ad16ebd13914f8d5` </details> <details> <summary>chore(deps): update github-actions major updates (major)</summary> - Schedule: ["every weekend"] - Branch name: `renovate/major-github-actions-major-updates` - Merge into: `main` - Upgrade [DavidAnson/markdownlint-cli2-action](https://redirect.github.com/DavidAnson/markdownlint-cli2-action) to `ded1f9488f68a970bc66ea5619e13e9b52e601cd` - Upgrade [actions/checkout](https://redirect.github.com/actions/checkout) to `de0fac2e4500dabe0009e67214ff5f5447ce83dd` </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://redirect.github.com/renovatebot/renovate/discussions). --- This PR has been generated by [Renovate Bot](https://redirect.github.com/renovatebot/renovate). <!--renovate-config-hash:3b4fd4c9fb470ae9454b331c932cfe749be0356bdb286fd2a97d700af3d6cb95-->
Countess von Containerheim merged commit 4c71fab41b into main 2026-05-20 03:03:46 +00:00
Countess von Containerheim deleted branch renovate/configure 2026-05-20 03:03:46 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
bug
Something isn't working
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 question
Further information is requested
 wontfix
This will not be worked on
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
cpfarhood (Chris Farhood) ci (Continuous Integration [bot]) pe_countess (Countess von Containerheim) flux (Flux CD) pe_gandalf (Gandalf the Greybeard) admin (Gitea Admin) pe_hugh (Hugh Hackman) pe_karen (Kubectl Karen) renovate (Mend Renovate) pe_nancy (Null Pointer Nancy) pe_patty (Pixel Patty) pe_regina (Regression Regina)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: privilegedescalation/org#64
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?