ops/dnflake
2
0
Fork 0
Code Issues Pull requests 1 Projects Releases Packages Activity Actions

chore: Configure Renovate #1

Open
Renovate-Bot wants to merge 1 commit from renovate/configure into main
pull from: renovate/configure
merge into: ops:main
Conversation 0 Commits 1 Files changed 1 +6
Renovate-Bot commented 2025-12-17 11:00:45 -08:00
Member
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

  • chef-workstation/Gemfile (bundler)
  • renovate.json (renovate-config-presets)

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
  • Pin Docker digests.
  • Pin github-action digests.
  • Enable Renovate configuration migration PRs when needed.
  • Pin dependency versions for development dependencies.
  • Recommended configuration for abandoned packages, treating packages without a release for 1 year as abandoned, while taking into account community-sourced overrides.
  • Wait until the npm package is three days old before raising the update. This a) introduces a short delay to allow for malware researchers and scanners to (possibly) detect any malicious behaviour in packages, and b) prevents the maintainer and/or NPM from unpublishing a package you already upgraded to, breaking builds.
  • Run lock file maintenance (updates) early Monday mornings.
  • Use semantic prefixes for commit messages and PR titles.

🔡 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 22 Pull Requests:

chore(deps): update dependency bcrypt_pbkdf to v1.1.2
  • Schedule: ["at any time"]
  • Branch name: renovate/bcrypt_pbkdf-1.x-lockfile
  • Merge into: main
  • Upgrade bcrypt_pbkdf to 1.1.2
chore(deps): update dependency chef to v18.8.54
  • Schedule: ["at any time"]
  • Branch name: renovate/chef-18.x-lockfile
  • Merge into: main
  • Upgrade chef to 18.8.54
chore(deps): update dependency chef-bin to v18.8.54
  • Schedule: ["at any time"]
  • Branch name: renovate/chef-bin-18.x-lockfile
  • Merge into: main
  • Upgrade chef-bin to 18.8.54
chore(deps): update dependency chef-cli to v5.6.23
  • Schedule: ["at any time"]
  • Branch name: renovate/chef-cli-5.x-lockfile
  • Merge into: main
  • Upgrade chef-cli to 5.6.23
chore(deps): update dependency chef-utils to v18.8.54
  • Schedule: ["at any time"]
  • Branch name: renovate/chef-utils-18.x-lockfile
  • Merge into: main
  • Upgrade chef-utils to 18.8.54
chore(deps): update dependency guard to v2.19.1
  • Schedule: ["at any time"]
  • Branch name: renovate/guard-2.x-lockfile
  • Merge into: main
  • Upgrade guard to 2.19.1
chore(deps): update dependency knife to v18.8.68
  • Schedule: ["at any time"]
  • Branch name: renovate/knife-18.x-lockfile
  • Merge into: main
  • Upgrade knife to 18.8.68
chore(deps): update dependency unf_ext to "~> 0.0.9.0"
  • Schedule: ["at any time"]
  • Branch name: renovate/unf_ext-0.x
  • Merge into: main
  • Upgrade unf_ext to "~> 0.0.9.0"
chore(deps): update dependency inspec-bin to v5.23.6
  • Schedule: ["at any time"]
  • Branch name: renovate/inspec-bin-5.x-lockfile
  • Merge into: main
  • Upgrade inspec-bin to 5.23.6
chore(deps): update dependency kitchen-dokken to v2.22.0
  • Schedule: ["at any time"]
  • Branch name: renovate/kitchen-dokken-2.x-lockfile
  • Merge into: main
  • Upgrade kitchen-dokken to 2.22.0
chore(deps): update dependency kitchen-vagrant to v2.2.0
  • Schedule: ["at any time"]
  • Branch name: renovate/kitchen-vagrant-2.x-lockfile
  • Merge into: main
  • Upgrade kitchen-vagrant to 2.2.0
chore(deps): update dependency mdl to v0.15.0
  • Schedule: ["at any time"]
  • Branch name: renovate/mdl-0.x-lockfile
  • Merge into: main
  • Upgrade mdl to 0.15.0
chore(deps): update dependency minitest to v5.27.0
  • Schedule: ["at any time"]
  • Branch name: renovate/minitest-5.x-lockfile
  • Merge into: main
  • Upgrade minitest to 5.27.0
chore(deps): update dependency pry to v0.15.2
  • Schedule: ["at any time"]
  • Branch name: renovate/pry-0.x
  • Merge into: main
  • Upgrade pry to "= 0.15.2"
chore(deps): update dependency rake to v13.3.1
  • Schedule: ["at any time"]
  • Branch name: renovate/rake-13.x
  • Merge into: main
  • Upgrade rake to "= 13.3.1"
chore(deps): update dependency rdoc to "~> 6.17.0"
  • Schedule: ["at any time"]
  • Branch name: renovate/rdoc-6.x
  • Merge into: main
  • Upgrade rdoc to "~> 6.17.0"
chore(deps): update dependency bson to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/bson-5.x-lockfile
  • Merge into: main
  • Upgrade bson to 5.2.0
chore(deps): update dependency cookstyle to v8
  • Schedule: ["at any time"]
  • Branch name: renovate/cookstyle-8.x-lockfile
  • Merge into: main
  • Upgrade cookstyle to 8.5.3
chore(deps): update dependency inspec-bin to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/inspec-bin-7.x
  • Merge into: main
  • Upgrade inspec-bin to "~> 7"
chore(deps): update dependency ohai to v19
  • Schedule: ["at any time"]
  • Branch name: renovate/ohai-19.x-lockfile
  • Merge into: main
  • Upgrade ohai to 19.0.3
chore(deps): update dependency openssl to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/openssl-4.x-lockfile
  • Merge into: main
  • Upgrade openssl to 4.0.0
chore(deps): lock file maintenance
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/lock-file-maintenance
  • Merge into: main
  • Regenerate lock files to use latest dependency versions

❓ 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 * `chef-workstation/Gemfile` (bundler) * `renovate.json` (renovate-config-presets) ### 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 - Pin Docker digests. - Pin `github-action` digests. - Enable Renovate configuration migration PRs when needed. - Pin dependency versions for development dependencies. - Recommended configuration for abandoned packages, treating packages without a release for 1 year as abandoned, while taking into account community-sourced overrides. - Wait until the npm package is three days old before raising the update. This a) introduces a short delay to allow for malware researchers and scanners to (possibly) detect any malicious behaviour in packages, and b) prevents the maintainer and/or NPM from unpublishing a package you already upgraded to, breaking builds. - Run lock file maintenance (updates) early Monday mornings. - Use semantic prefixes for commit messages and PR titles. 🔡 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 22 Pull Requests: <details> <summary>chore(deps): update dependency bcrypt_pbkdf to v1.1.2</summary> - Schedule: ["at any time"] - Branch name: `renovate/bcrypt_pbkdf-1.x-lockfile` - Merge into: `main` - Upgrade [bcrypt_pbkdf](https://github.com/net-ssh/bcrypt_pbkdf-ruby) to `1.1.2` </details> <details> <summary>chore(deps): update dependency chef to v18.8.54</summary> - Schedule: ["at any time"] - Branch name: `renovate/chef-18.x-lockfile` - Merge into: `main` - Upgrade [chef](https://github.com/chef/chef) to `18.8.54` </details> <details> <summary>chore(deps): update dependency chef-bin to v18.8.54</summary> - Schedule: ["at any time"] - Branch name: `renovate/chef-bin-18.x-lockfile` - Merge into: `main` - Upgrade [chef-bin](https://github.com/chef/chef) to `18.8.54` </details> <details> <summary>chore(deps): update dependency chef-cli to v5.6.23</summary> - Schedule: ["at any time"] - Branch name: `renovate/chef-cli-5.x-lockfile` - Merge into: `main` - Upgrade chef-cli to `5.6.23` </details> <details> <summary>chore(deps): update dependency chef-utils to v18.8.54</summary> - Schedule: ["at any time"] - Branch name: `renovate/chef-utils-18.x-lockfile` - Merge into: `main` - Upgrade [chef-utils](https://github.com/chef/chef) to `18.8.54` </details> <details> <summary>chore(deps): update dependency guard to v2.19.1</summary> - Schedule: ["at any time"] - Branch name: `renovate/guard-2.x-lockfile` - Merge into: `main` - Upgrade [guard](https://github.com/guard/guard) to `2.19.1` </details> <details> <summary>chore(deps): update dependency knife to v18.8.68</summary> - Schedule: ["at any time"] - Branch name: `renovate/knife-18.x-lockfile` - Merge into: `main` - Upgrade [knife](https://github.com/chef/chef) to `18.8.68` </details> <details> <summary>chore(deps): update dependency unf_ext to "~> 0.0.9.0"</summary> - Schedule: ["at any time"] - Branch name: `renovate/unf_ext-0.x` - Merge into: `main` - Upgrade [unf_ext](https://github.com/knu/ruby-unf_ext) to `"~> 0.0.9.0"` </details> <details> <summary>chore(deps): update dependency inspec-bin to v5.23.6</summary> - Schedule: ["at any time"] - Branch name: `renovate/inspec-bin-5.x-lockfile` - Merge into: `main` - Upgrade [inspec-bin](https://github.com/inspec/inspec) to `5.23.6` </details> <details> <summary>chore(deps): update dependency kitchen-dokken to v2.22.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/kitchen-dokken-2.x-lockfile` - Merge into: `main` - Upgrade [kitchen-dokken](https://github.com/test-kitchen/kitchen-dokken) to `2.22.0` </details> <details> <summary>chore(deps): update dependency kitchen-vagrant to v2.2.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/kitchen-vagrant-2.x-lockfile` - Merge into: `main` - Upgrade [kitchen-vagrant](https://github.com/opscode/kitchen-vagrant) to `2.2.0` </details> <details> <summary>chore(deps): update dependency mdl to v0.15.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/mdl-0.x-lockfile` - Merge into: `main` - Upgrade [mdl](https://github.com/mivok/markdownlint) to `0.15.0` </details> <details> <summary>chore(deps): update dependency minitest to v5.27.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/minitest-5.x-lockfile` - Merge into: `main` - Upgrade [minitest](https://github.com/minitest/minitest) to `5.27.0` </details> <details> <summary>chore(deps): update dependency pry to v0.15.2</summary> - Schedule: ["at any time"] - Branch name: `renovate/pry-0.x` - Merge into: `main` - Upgrade [pry](https://github.com/pry/pry) to `"= 0.15.2"` </details> <details> <summary>chore(deps): update dependency rake to v13.3.1</summary> - Schedule: ["at any time"] - Branch name: `renovate/rake-13.x` - Merge into: `main` - Upgrade [rake](https://github.com/ruby/rake) to `"= 13.3.1"` </details> <details> <summary>chore(deps): update dependency rdoc to "~> 6.17.0"</summary> - Schedule: ["at any time"] - Branch name: `renovate/rdoc-6.x` - Merge into: `main` - Upgrade [rdoc](https://github.com/ruby/rdoc) to `"~> 6.17.0"` </details> <details> <summary>chore(deps): update dependency bson to v5</summary> - Schedule: ["at any time"] - Branch name: `renovate/bson-5.x-lockfile` - Merge into: `main` - Upgrade [bson](https://github.com/mongodb/bson-ruby) to `5.2.0` </details> <details> <summary>chore(deps): update dependency cookstyle to v8</summary> - Schedule: ["at any time"] - Branch name: `renovate/cookstyle-8.x-lockfile` - Merge into: `main` - Upgrade [cookstyle](https://github.com/chef/cookstyle) to `8.5.3` </details> <details> <summary>chore(deps): update dependency inspec-bin to v7</summary> - Schedule: ["at any time"] - Branch name: `renovate/inspec-bin-7.x` - Merge into: `main` - Upgrade [inspec-bin](https://github.com/inspec/inspec) to `"~> 7"` </details> <details> <summary>chore(deps): update dependency ohai to v19</summary> - Schedule: ["at any time"] - Branch name: `renovate/ohai-19.x-lockfile` - Merge into: `main` - Upgrade [ohai](https://github.com/chef/ohai) to `19.0.3` </details> <details> <summary>chore(deps): update dependency openssl to v4</summary> - Schedule: ["at any time"] - Branch name: `renovate/openssl-4.x-lockfile` - Merge into: `main` - Upgrade [openssl](https://github.com/ruby/openssl) to `4.0.0` </details> <details> <summary>chore(deps): lock file maintenance</summary> - Schedule: ["* 0-3 * * 1"] - Branch name: `renovate/lock-file-maintenance` - Merge into: `main` - Regenerate lock files to use latest dependency versions </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:60ae7e708ff8835679ac3a90548977c50f368aa53ce48909a5fe28762009a8de-->
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 switch renovate/configure

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff renovate/configure
git switch renovate/configure
git rebase main
git switch main
git merge --ff-only renovate/configure
git switch renovate/configure
git rebase main
git switch main
git merge --no-ff renovate/configure
git switch main
git merge --squash renovate/configure
git switch main
git merge --ff-only renovate/configure
git switch main
git merge renovate/configure
git push origin main
Sign in to join this conversation.
Reviewers
No reviewers
onlyhavecans
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
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
ops/dnflake!1
No description provided.