Auto discover dependency issues
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 4.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 205
Description
Implement a test to uncover dependency issues early on:
- alert when a new version is available
- there are potential conflicts
- it is possible to relax pinned version or upper bounds.
One idea:
"""
set up a nightly that relaxes some of the
requirements and sees what (if anything) breaks. Not breaking is
likely a signal that we should relax ours.
"""
context: https://lists.apache.org/thread.html/f3abf35b2d01e21c72460404d3b58fb2aa50892379e6eae46799f5f5@%3Cdev.beam.apache.org%3E
Imported from Jira [BEAM-3363](https://issues.apache.org/jira/browse/BEAM-3363). Original Jira may contain additional context.
Reported by: altay.
Contributor guide
Research direction
No files, tests, or entry points are named. Start by reviewing the repository's dependency configuration and the linked BEAM-3363 context to identify where dependency checks and nightly automation belong. Done means an automated check reports available versions, potential conflicts, and pins or upper bounds that can be safely relaxed.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100