Skip to content

[CI] Create dependabot.yml for version updating #66

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Sep 6, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
77 changes: 77 additions & 0 deletions .github/dependabot.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,77 @@
# To get started with Dependabot version updates, you'll need to specify which
# package ecosystems to update and where the package manifests are located.
# Please see the documentation for all configuration options:
# https://docs.github.com/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file

# This Dependabot configuration file is set up to manage dependency updates for both Python packages (pip) and GitHub Actions workflows.
#
# Key points:
# - Dependencies are categorized into production and development groups.
# - The "setuptools" package is treated as an exception: it is excluded from the production group but is still allowed to be updated as a production dependency.
# - The configuration includes specific labels, assignees, and commit message formats to streamline the update process.
# - Updates are scheduled to run weekly on Tuesdays.

version: 2
updates:
- package-ecosystem: "pip" # See documentation for possible values
directory: "/" # Location of package manifests
milestone: 2
target-branch: "master"
versioning-strategy: increase-if-necessary
# Labels on pull requests for version updates only
labels:
- "Configs"
- "Version Update"
- "Python Lang"
- "Python Repo"
groups:
production-dependencies:
dependency-type: "production"
exclude-patterns:
- "setuptools*"
development-dependencies:
dependency-type: "development"
allow:
- dependency-name: "setuptools"
dependency-type: "production"
- dependency-name: "pip"
dependency-type: "direct"
- dependency-name: "wheel"
dependency-type: "production"
- dependency-name: "build"
dependency-type: "production"
- dependency-name: "argparse"
dependency-type: "direct"
- dependency-name: "six"
dependency-type: "direct"
- dependency-name: "tox"
dependency-type: "development"
- dependency-name: "virtualenv"
dependency-type: "development"
assignees:
- "reactive-firewall"
commit-message:
prefix: "[HOTFIX] "
include: "scope"
schedule:
interval: "weekly"
day: "tuesday"
- package-ecosystem: "github-actions" # See documentation for possible values
directory: ".github/workflows/" # Location of package manifests
milestone: 2
target-branch: "master"
# Labels on pull requests for version updates only
labels:
- "Configs"
- "Version Update"
- "GitHub"
- "Testing"
- "Python Repo"
assignees:
- "reactive-firewall"
commit-message:
prefix: "[UPDATE] "
include: "scope"
schedule:
interval: "weekly"
day: "tuesday"