Related Slack conversation here
In the workflows jobs:
All dependabot updates workflow runs share one workflow ID, which means that we are always reporting the status of the latest run of any dependabot workflow.
This means that we are not getting alerts for some failing runs if they are followed by a successful run for an unrelated ecosystem (e.g. failing uv updates followed by successful github actions updates). We could add in some custom logic to separate out different dependabot workflows.
This ticket is currently low priority since we are doing weekly uv dependency updates using https://github.com/bennettoxford/update-dependencies-action anyway.
Related Slack conversation here
In the
workflowsjobs:All dependabot updates workflow runs share one workflow ID, which means that we are always reporting the status of the latest run of any dependabot workflow.
This means that we are not getting alerts for some failing runs if they are followed by a successful run for an unrelated ecosystem (e.g. failing
uvupdates followed by successful github actions updates). We could add in some custom logic to separate out different dependabot workflows.This ticket is currently low priority since we are doing weekly
uvdependency updates using https://github.com/bennettoxford/update-dependencies-action anyway.