|
| 1 | +# To get started with Dependabot version updates, you'll need to specify which |
| 2 | +# package ecosystems to update and where the package manifests are located. |
| 3 | +# Please see the documentation for all configuration options: |
| 4 | +# https://docs.github.com/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file |
| 5 | + |
| 6 | +# This Dependabot configuration file is set up to manage dependency updates for both Python packages (pip) and GitHub Actions workflows. |
| 7 | +# |
| 8 | +# Key points: |
| 9 | +# - Dependencies are categorized into production and development groups. |
| 10 | +# - 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. |
| 11 | +# - The configuration includes specific labels, assignees, and commit message formats to streamline the update process. |
| 12 | +# - Updates are scheduled to run weekly on Tuesdays. |
| 13 | + |
| 14 | +version: 2 |
| 15 | +updates: |
| 16 | + - package-ecosystem: "pip" # See documentation for possible values |
| 17 | + directory: "/" # Location of package manifests |
| 18 | + milestone: 2 |
| 19 | + target-branch: "master" |
| 20 | + versioning-strategy: increase-if-necessary |
| 21 | + # Labels on pull requests for version updates only |
| 22 | + labels: |
| 23 | + - "Configs" |
| 24 | + - "Version Update" |
| 25 | + - "Python Lang" |
| 26 | + - "Python Repo" |
| 27 | + groups: |
| 28 | + production-dependencies: |
| 29 | + dependency-type: "production" |
| 30 | + exclude-patterns: |
| 31 | + - "setuptools*" |
| 32 | + development-dependencies: |
| 33 | + dependency-type: "development" |
| 34 | + allow: |
| 35 | + - dependency-name: "setuptools" |
| 36 | + dependency-type: "production" |
| 37 | + - dependency-name: "pip" |
| 38 | + dependency-type: "direct" |
| 39 | + - dependency-name: "wheel" |
| 40 | + dependency-type: "production" |
| 41 | + - dependency-name: "build" |
| 42 | + dependency-type: "production" |
| 43 | + - dependency-name: "argparse" |
| 44 | + dependency-type: "direct" |
| 45 | + - dependency-name: "six" |
| 46 | + dependency-type: "direct" |
| 47 | + - dependency-name: "tox" |
| 48 | + dependency-type: "development" |
| 49 | + - dependency-name: "virtualenv" |
| 50 | + dependency-type: "development" |
| 51 | + assignees: |
| 52 | + - "reactive-firewall" |
| 53 | + commit-message: |
| 54 | + prefix: "[HOTFIX] " |
| 55 | + include: "scope" |
| 56 | + schedule: |
| 57 | + interval: "weekly" |
| 58 | + day: "tuesday" |
| 59 | + - package-ecosystem: "github-actions" # See documentation for possible values |
| 60 | + directory: ".github/workflows/" # Location of package manifests |
| 61 | + milestone: 2 |
| 62 | + target-branch: "master" |
| 63 | + # Labels on pull requests for version updates only |
| 64 | + labels: |
| 65 | + - "Configs" |
| 66 | + - "Version Update" |
| 67 | + - "GitHub" |
| 68 | + - "Testing" |
| 69 | + - "Python Repo" |
| 70 | + assignees: |
| 71 | + - "reactive-firewall" |
| 72 | + commit-message: |
| 73 | + prefix: "[UPDATE] " |
| 74 | + include: "scope" |
| 75 | + schedule: |
| 76 | + interval: "weekly" |
| 77 | + day: "tuesday" |
0 commit comments