Repository navigation
chore(ci): add a Dependabot config - #3
Merged
Merged
Conversation
The pinned dependencies here had no watcher. CompatHelper, where it runs, reads Julia [compat] bounds and never looks at workflows, so pinned actions drift until a runner image change breaks them. Weekly, one PR per dependency rather than a combined bump, so a failure is attributable to the dependency that caused it. Assisted-by: AI
Welcome to Codecov 🎉Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests. Thanks for integrating Codecov - We've got you covered ☂️ |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Nothing watched this repository's pinned dependencies.
CompatHelper, where it runs, reads Julia
[compat]bounds and never looks at workflows, so pinned actions drift silently until a runner image change breaks them. That is not hypothetical: elsewhere in this estatejulia-actions/setup-juliav3 began rejectingarch: x64on Apple Silicon runners, and two repositories had macOS legs that had never run as a result.Ecosystems watched: github-actions
Weekly, one pull request per dependency rather than a combined bump, so a failure stays attributable to the dependency that caused it. That matters most across a major version: a bot updates the version string, never the configuration the new major expects.
Dependabot has no Julia ecosystem, so
[compat]bounds remain CompatHelper's job.Assisted by AI.