Configure Renovate

[ms-gh-admin]

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/requirements.txt (pip_requirements)
• pyproject.toml (poetry)

Configuration

🔡 Renovate has detected a custom config for this PR. Feel free to ask for help if you have any doubts and would like it reviewed.

Important: Now that this branch is edited, Renovate can't rebase it from the base branch any more. If you make changes to the base branch that could impact this onboarding PR, please merge them manually.

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

What to Expect

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

Update dependency bandit to v1.7.4

• Schedule: ["at any time"]
• Branch name: renovate/bandit-1.x-lockfile
• Merge into: develop
• Upgrade bandit to 1.7.4

Update dependency coverage to v6.4.2

• Schedule: ["at any time"]
• Branch name: renovate/coverage-6.x-lockfile
• Merge into: develop
• Upgrade coverage to 6.4.2

Update dependency redis to v4.3.4

• Schedule: ["at any time"]
• Branch name: renovate/redis-4.x-lockfile
• Merge into: develop
• Upgrade redis to 4.3.4

Update dependency types-toml to v0.10.8

• Schedule: ["at any time"]
• Branch name: renovate/types-toml-0.x-lockfile
• Merge into: develop
• Upgrade types-toml to 0.10.8

Update dependency black to v22.6.0

• Schedule: ["at any time"]
• Branch name: renovate/black-22.x-lockfile
• Merge into: develop
• Upgrade black to 22.6.0

Update dependency mypy to v0.971

• Schedule: ["at any time"]
• Branch name: renovate/mypy-0.x-lockfile
• Merge into: develop
• Upgrade mypy to 0.971

Update dependency pytest to v7.1.2

• Schedule: ["at any time"]
• Branch name: renovate/pytest-7.x-lockfile
• Merge into: develop
• Upgrade pytest to 7.1.2

Update dependency types-redis to v4.3.7

• Schedule: ["at any time"]
• Branch name: renovate/types-redis-4.x-lockfile
• Merge into: develop
• Upgrade types-redis to 4.3.7

Update dependency yamllint to v1.27.1

• Schedule: ["at any time"]
• Branch name: renovate/yamllint-1.x-lockfile
• Merge into: develop
• Upgrade yamllint to 1.27.1

Update dependency flake8 to v4

• Schedule: ["at any time"]
• Branch name: renovate/flake8-4.x-lockfile
• Merge into: develop
• Upgrade flake8 to 4.0.1

🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or spam 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 has been generated by Renovate Bot.

[Kircheneer]

@glennmatthews  @chadell I personally think there would be value in including all of the files, including the requirements.txt files for the examples. My suggestion would be to follow something similar to what Nautobot does for renovate and then batch the changes for the example files to something like once a month so it's not as noisy. Opinions?

[chadell]

what Nautobot does for renovate

It makes sense to me. @glennmatthews would make sense to apply this to all the repos?

[chadell]

LGTM
question: would make sense to add this in our cookiecutter to keep consistency?

[Kircheneer]

LGTM question: would make sense to add this in our cookiecutter to keep consistency?

I wasn't really 100% done here, but I might just throw it out there like this for now and then iterate upon it similar to what was done in the Nautobot repo. Anyway, I'd like to hold off on contributing this until I have something that I know works well.