Add dependabot version scanning config - #132
Conversation
NeethuESim
left a comment
There was a problem hiding this comment.
@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:
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. |
|
cool. STESOL-557 will prevent any accidental merging for any PRs without the integration/unit tests passing. |
839dfa9 to
6d52493
Compare
There was a problem hiding this comment.
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-generationand/mcp-local(both containuv.lock). - Configure monthly Dependabot updates for root Python dependencies using the
pipecosystem.
💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.
Adds Dependabot version scanning for Github Actions workflows and our various
uv/pipenvironments. 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.