ComputerSurge/bind9
3
0
Fork 0
Code Pull Requests 1 Activity

chore: Configure Renovate #1

Open
Renovate wants to merge 1 commits from renovate/configure into main
pull from: renovate/configure
merge into: ComputerSurge:main
Conversation 0 Commits 1 Files Changed 1 +6
Renovate commented 2026-02-12 10:02:10 -06: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

  • .github/workflows/codeql.yml (github-actions)
  • .github/workflows/lockdown.yml (github-actions)
  • .github/workflows/sonarcloud.yml (github-actions)
  • .gitlab-ci.yml (gitlabci)
  • doc/arm/requirements.txt (pip_requirements)

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.
  • Show only the Age and Confidence Merge Confidence badges for pull requests.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.
  • Ensure that every dependency pinned by digest and sourced from GitHub.com contains a link to the commit-to-commit diff
  • Correctly link to the source code for golang.org/x packages
  • Link to pkg.go.dev/... for golang.org/x packages' title

🔡 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.

What to Expect

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

chore(deps): update dependency sphinx to v8.2.3
  • Schedule: ["at any time"]
  • Branch name: renovate/sphinx-8.x
  • Merge into: main
  • Upgrade Sphinx to ==8.2.3
chore(deps): update dependency docutils to v0.22.4
  • Schedule: ["at any time"]
  • Branch name: renovate/docutils-0.x
  • Merge into: main
  • Upgrade docutils to ==0.22.4
chore(deps): update dependency sphinx_rtd_theme to v3.1.0
  • Schedule: ["at any time"]
  • Branch name: renovate/sphinx_rtd_theme-3.x
  • Merge into: main
  • Upgrade sphinx_rtd_theme to ==3.1.0
chore(deps): update dependency sphinx to v9
  • Schedule: ["at any time"]
  • Branch name: renovate/sphinx-9.x
  • Merge into: main
  • Upgrade Sphinx to ==9.1.0

🚸 PR creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm the project. See docs for prHourlyLimit for details.

⚠️ Warning

Please correct - or verify that you can safely ignore - these dependency lookup failures before you merge this PR.

  • Failed to look up github-tags package actions/checkout
  • Failed to look up github-digest package awalsh128/cache-apt-pkgs-action
  • Failed to look up github-tags package github/codeql-action
  • Failed to look up github-tags package dessant/repo-lockdown
  • Failed to look up github-tags package SonarSource/sonarcloud-github-c-cpp

Files affected: .github/workflows/codeql.yml, .github/workflows/lockdown.yml, .github/workflows/sonarcloud.yml

❓ 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 * `.github/workflows/codeql.yml` (github-actions) * `.github/workflows/lockdown.yml` (github-actions) * `.github/workflows/sonarcloud.yml` (github-actions) * `.gitlab-ci.yml` (gitlabci) * `doc/arm/requirements.txt` (pip_requirements) ### 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. - Show only the Age and Confidence Merge Confidence badges for pull requests. - Apply crowd-sourced package replacement rules. - Apply crowd-sourced workarounds for known problems with packages. - Ensure that every dependency pinned by digest and sourced from GitHub.com contains a link to the commit-to-commit diff - Correctly link to the source code for golang.org/x packages - Link to pkg.go.dev/... for golang.org/x packages' title 🔡 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. --- ### What to Expect With your current configuration, Renovate will create 4 Pull Requests: <details> <summary>chore(deps): update dependency sphinx to v8.2.3</summary> - Schedule: ["at any time"] - Branch name: `renovate/sphinx-8.x` - Merge into: `main` - Upgrade [Sphinx](https://github.com/sphinx-doc/sphinx) to `==8.2.3` </details> <details> <summary>chore(deps): update dependency docutils to v0.22.4</summary> - Schedule: ["at any time"] - Branch name: `renovate/docutils-0.x` - Merge into: `main` - Upgrade [docutils](https://sourceforge.net/p/docutils/code/) to `==0.22.4` </details> <details> <summary>chore(deps): update dependency sphinx_rtd_theme to v3.1.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/sphinx_rtd_theme-3.x` - Merge into: `main` - Upgrade [sphinx_rtd_theme](https://github.com/readthedocs/sphinx_rtd_theme) to `==3.1.0` </details> <details> <summary>chore(deps): update dependency sphinx to v9</summary> - Schedule: ["at any time"] - Branch name: `renovate/sphinx-9.x` - Merge into: `main` - Upgrade [Sphinx](https://github.com/sphinx-doc/sphinx) to `==9.1.0` </details> 🚸 PR creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm the project. See [docs for `prHourlyLimit`](https://docs.renovatebot.com/configuration-options/#prhourlylimit) for details. --- > > ⚠️ **Warning** > > Please correct - or verify that you can safely ignore - these dependency lookup failures before you merge this PR. > > - `Failed to look up github-tags package actions/checkout` > - `Failed to look up github-digest package awalsh128/cache-apt-pkgs-action` > - `Failed to look up github-tags package github/codeql-action` > - `Failed to look up github-tags package dessant/repo-lockdown` > - `Failed to look up github-tags package SonarSource/sonarcloud-github-c-cpp` > > Files affected: `.github/workflows/codeql.yml`, `.github/workflows/lockdown.yml`, `.github/workflows/sonarcloud.yml` --- ❓ 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:e80b4e42a3043bc12fa0640db4bac392d2bf770acf841360d7c8ceeeac2ec1a9-->
Renovate added 1 commit 2026-02-12 10:02:12 -06:00
Add renovate.json 48188dbf5d
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin renovate/configure:renovate/configure
git checkout renovate/configure
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
Komodo ninjasurge Renovate
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: ComputerSurge/bind9#1
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?