There seems to be a suggestion in Scala-3 that libraries should follow LTS releases, and apps should follow any release.
Might it be useful to allow the user - through an build.sbt property - to set the strategy to follow, so you would have something like:-
dependencyUpdates / strategy := "LTS"
and then only LTS releases would be suggested as updates.
This also opens the possibility to have multiple strategies, so you might have one which followed -RCs where the normal strategy might ignore -RCs.
Exactly how the plugin would know that something is an LTS release is perhaps more troublesome. There is a formula for the scala-3 compiler, but in spite of the suggestion being made (I think Seth Tisue was the one who made it a while ago on Discord) I am not sure that a marking scheme has been put forward, but perhaps a discussion could be had with the Scala Centre as to how they intended that this suggestion was to be implemented. I also do not know if the Scala Steward is going to attempt the same thing.
There seems to be a suggestion in Scala-3 that libraries should follow LTS releases, and apps should follow any release.
Might it be useful to allow the user - through an build.sbt property - to set the strategy to follow, so you would have something like:-
and then only LTS releases would be suggested as updates.
This also opens the possibility to have multiple strategies, so you might have one which followed -RCs where the normal strategy might ignore -RCs.
Exactly how the plugin would know that something is an LTS release is perhaps more troublesome. There is a formula for the scala-3 compiler, but in spite of the suggestion being made (I think Seth Tisue was the one who made it a while ago on Discord) I am not sure that a marking scheme has been put forward, but perhaps a discussion could be had with the Scala Centre as to how they intended that this suggestion was to be implemented. I also do not know if the Scala Steward is going to attempt the same thing.