Configure Renovate

[renovate]

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

• docs/Gemfile (bundler)
• .github/workflows/Comment-on-PR.yml (github-actions)
• .github/workflows/Notify-Convention-Change.yml (github-actions)
• .github/workflows/PR.yml (github-actions)
• .github/workflows/Publish-Package.yml (github-actions)
• .github/workflows/Update-Poetry-Lock.yml (github-actions)
• pyproject.toml (poetry)
• .github/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
• Hopefully safe environment variables to allow users to configure.
• Show all Merge Confidence badges for pull requests.
• 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.
• Raise PR when vulnerability alerts are detected.
• Raise PR when vulnerability alerts are detected (including OSV alerts).
• Convert pinned GitHub Action digests to SemVer.
• Run lock file maintenance (updates) on the first day of each month.
• Rebase existing PRs any time the base branch has been updated.

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

chore(deps): update ruby packages

• Schedule: ["* 0-3 * * 1"]
• Branch name: users/renovate/ruby
• Merge into: main
• Upgrade tzinfo to 1.2.11
• Upgrade tzinfo-data to 1.2025.2
• Upgrade wdm to "~> 0.2.0"

fix(deps): update python packages

• Schedule: ["* 0-3 * * 1"]
• Branch name: users/renovate/python
• Merge into: main
• Upgrade better-diff to 0.1.4
• Upgrade black to 24.10.0
• Upgrade click to 8.3.0
• Upgrade flake8-black to 0.4.0
• Upgrade flake8-import-order to >=0.19.2,<0.20.0
• Upgrade isort to 5.13.2
• Upgrade pathspec to 0.12.1
• Upgrade pep8-naming to 0.15.1

chore(deps): update github actions

• Schedule: ["* 0-3 * * 1"]
• Branch name: users/renovate/github-actions
• Merge into: main
• Upgrade actions/cache to 0057852bfaa89a56745cba8c7296529d2fc39830
• Upgrade actions/checkout to ee0669bd1cc54295c223e0bb666b733df41de1c5
• Upgrade actions/checkout to 08eba0b27e820071cde6df949e0beb9ba4906955
• Upgrade actions/checkout to f43a0e5ff2bd294095638e18286ca9a3d1956744
• Upgrade actions/setup-python to e9aba2c848f5ebd159c070c61ea2c4e2b122355e
• Upgrade ni/python-actions to 9768589f3e50672173dad75a6fc181e4a85d33fa
• Upgrade pypa/gh-action-pypi-publish to ed0c53931b1dc9bd32cbe73a98c7f6766f8a527e
• Upgrade thollander/actions-comment-pull-request to 8a3fad13c20088e9eb0805666b9fe49509d2fec8

chore(deps): update github actions (major)

• Schedule: ["* 0-3 * * 1"]
• Branch name: users/renovate/major-github-actions
• Merge into: main
• Upgrade actions/checkout to 08c6903cd8c0fde910a37f88322edcfb5dd907a8
• Upgrade actions/download-artifact to 634f93cb2916e3fdff6788551b99b062d0335ce0
• Upgrade actions/setup-python to e797f83bcb11b83ae66e0230d6156d7c80228e7c
• Upgrade thollander/actions-comment-pull-request to 24bffb9b452ba05a4f3f77933840a6a841d1b32b

chore(deps): update python packages (major)

• Schedule: ["* 0-3 * * 1"]
• Branch name: users/renovate/major-python
• Merge into: main
• Upgrade black to 25.9.0
• Upgrade isort to 6.1.0
• Upgrade pytest to 8.4.2

chore(deps): update ruby packages (major)

• Schedule: ["* 0-3 * * 1"]
• Branch name: users/renovate/major-ruby
• Merge into: main
• Upgrade github-pages to "~> 232"
• Upgrade tzinfo to "~> 2.0"

chore(deps): lock file maintenance

• Schedule: ["* 0-3 1 * *"]
• Branch name: users/renovate/lock-file-maintenance
• Merge into: main
• Regenerate lock files to use latest dependency versions

🚸 Branch 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.

---

❓ 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 was generated by Mend Renovate. View the repository job log.

[github-actions]

Thank you for contributing! 👋

[mshafer-NI]

Note that immediately switching from the default config to NI's config for Python packages means that we will NOT get the "what to expect", and instead can expect only Python packages updated for now, as specified here

[bkeryan]

Note that immediately switching from the default config to NI's config for Python packages means that we will NOT get the "what to expect", and instead can expect only Python packages updated for now, as specified here

That's not correct. ni/python-renovate-config doesn't limit the datasources or managers, so you will still get Ruby bundler updates. They will not be grouped or scheduled, so there will be a separate PR for each Ruby gem.

Consider doing something like this (untested):

{
    "packageRules": [
        {
            "description": "Update Ruby packages early Monday mornings.",
            "matchCategories": [
                "ruby"
            ],
            "matchUpdateTypes": [
                "major",
                "minor",
                "patch",
                "rollback",
                "replacement"
            ],
            "groupName": "Ruby packages",
            "groupSlug": "ruby",
            "extends": [
                "schedule:weekly"
            ]
        }
    ]
}

[bkeryan]

Note that immediately switching from the default config to NI's config for Python packages means that we will NOT get the "what to expect", and instead can expect only Python packages updated for now, as specified here

That's not correct. ni/python-renovate-config doesn't limit the datasources or managers, so you will still get Ruby bundler updates. They will not be grouped or scheduled, so there will be a separate PR for each Ruby gem.

PR for this: #240

[bkeryan]

@mshafer-NI @irwand @neilvana BTW, you should also update the repo's "Advanced Security" settings:

• Make sure "Dependency Graph" is enabled.
• Make sure "Dependabot alerts" is enabled.
• Make sure other Dependabot features are disabled