Skip to content

Add dependabot version scanning config - #132

Merged
brikin01 merged 6 commits into
mainfrom
add-dependabot-version-scanning
Aug 20, 2026
Merged

Add dependabot version scanning config#132
brikin01 merged 6 commits into
mainfrom
add-dependabot-version-scanning

Conversation

@brikin01

@brikin01 brikin01 commented Aug 6, 2026

Copy link
Copy Markdown
Collaborator

Adds Dependabot version scanning for Github Actions workflows and our various uv/pip environments. This is in addition to the security scanning that is already present. To reduce the amount of PR noise, I've set it to run monthly and group all updates into one PR for each package manager environment. We can easily change this to more or less often as desired in the future.

@NeethuESim NeethuESim left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

@brikin01 one danger I see with this version package update is regression issues. Existing flows might break because of incompatibility between packages after upgrade. Can you add some dependency here that update should be made only after the integration & unit tests pass with these changes ? Or if these changes are made after PR creation, then merge should be allowed only if all the integration & unit tests pass.

@brikin01

brikin01 commented Aug 6, 2026

Copy link
Copy Markdown
Collaborator Author

@brikin01 one danger I see with this version package update is regression issues. Existing flows might break because of incompatibility between packages after upgrade. Can you add some dependency here that update should be made only after the integration & unit tests pass with these changes ? Or if these changes are made after PR creation, then merge should be allowed only if all the integration & unit tests pass.

The typical flow is:

  1. Dependabot runs on a weekly cadence
  2. If it detects a version can/should be updated, it will open a PR for those updates, thus triggering any CI workflows we have.
  3. We still then need to manually review and merge it.

So I think there shouldn't be a problem there, in that our tests should catch any regressions before we ever merge. And from there we could either close the Dependabot PR or figure out how to use the latest version without breaking CI. Any rules around requiring tests to pass before merging will just be a matter of having stricter rules on our main branch, which I believe is part of the work of STESOL-557.

@NeethuESim

Copy link
Copy Markdown
Collaborator

STESOL-557

cool. STESOL-557 will prevent any accidental merging for any PRs without the integration/unit tests passing.

@brikin01
brikin01 changed the base branch from secure-build to main August 20, 2026 14:47
@brikin01
brikin01 force-pushed the add-dependabot-version-scanning branch from 839dfa9 to 6d52493 Compare August 20, 2026 14:52
@brikin01
brikin01 marked this pull request as ready for review August 20, 2026 15:55
Copilot AI lite review requested due to automatic review settings August 20, 2026 15:55

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 new Dependabot configuration to enable automated dependency update PRs across this repository, covering GitHub Actions and Python dependencies in multiple subprojects.

Changes:

  • Configure monthly Dependabot updates for GitHub Actions workflows at the repository root.
  • Configure monthly Dependabot updates for uv-managed Python projects under /embedding-generation and /mcp-local (both contain uv.lock).
  • Configure monthly Dependabot updates for root Python dependencies using the pip ecosystem.

💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.

@brikin01
brikin01 merged commit 8ae834c into main Aug 20, 2026
10 checks passed
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.

4 participants