I think one of the solutions to this problem would be to have the resolver list very clearly which packages have upper bounds that do not correspond to the latest release of a package. That way people can easily complain to these packages or make PRs to raise upper bounds, or remove these packages (possibly by using a separate environment).
nalimilan
69
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Announcement: automatic merging for the General registry | 64 | 5127 | December 23, 2019 | |
| Dependency problem with FIllArrays | 41 | 2543 | April 26, 2019 | |
| Bounds on package versions | 10 | 1087 | March 5, 2020 | |
| New automerge requirement: Release notes required for breaking package releases | 50 | 1839 | January 2, 2025 | |
| Would slowing Julia's release cadence improve ecosystem quality? | 98 | 5777 | September 15, 2023 |