Skip to content

chore: add enterprise Dependabot configuration - #778

Open
somethingwithproof wants to merge 2 commits into
Cacti:developfrom
somethingwithproof:chore/dependabot-config
Open

chore: add enterprise Dependabot configuration#778
somethingwithproof wants to merge 2 commits into
Cacti:developfrom
somethingwithproof:chore/dependabot-config

Conversation

@somethingwithproof

Copy link
Copy Markdown
Contributor

Adds grouped, cooled-down Dependabot updates with standard ecosystem labels and commit prefixes.

Copilot AI review requested due to automatic review settings July 14, 2026 17:51

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a Dependabot configuration to automate and standardize GitHub Actions dependency updates for the thold plugin repository, reducing update noise while keeping workflows current.

Changes:

  • Introduces .github/dependabot.yml with weekly scheduled GitHub Actions updates targeting the develop branch.
  • Enables grouped updates (single group matching all actions), applies standard labels, and standardizes commit message prefix/scope.
  • Adds a 7-day cooldown window to avoid immediate PRs for newly released versions.

@somethingwithproof
somethingwithproof force-pushed the chore/dependabot-config branch from b6e3fa2 to f6ef025 Compare July 29, 2026 03:35
@somethingwithproof

Copy link
Copy Markdown
Contributor Author

Rebased onto current develop (branch was 11 commits behind). No Copilot review threads to address.

The Integration Test failures are unrelated to this PR's diff (adds .github/dependabot.yml only, no workflow changes). Root cause: apt-get install ... libapache2-mod-php{8.1,8.2,8.4} fails with "Unable to locate package" on the ubuntu-latest runner image, since the default apt repos only ship libapache2-mod-php8.3. This also fails on the latest push to develop (run 26199721468, 2026-05-21), so it's a pre-existing repo-wide CI infra issue, not something introduced here. Not fixing it as part of this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants