This seems similar to https://github.com/spring-projects/spring-boot/issues/34307. We're using Framework 6.1.0-M1 at the moment. moveToSnapshots didn't offer 6.1.0-SNAPSHOT ahead of next week's 6.1.0-M2 release and it should have.
Comment From: snicoll
bomr does no longer offer an available milestone upgrade either. We were using Spring Security 6.2.0-SNAPSHOT and bomrUpgrade did not suggest 6.2.0-M1.
Comment From: wilkinsona
If we consider a -SNAPSHOT to be later than an Mn, it will never offer the milestone. If we consider an Mn to be later than a -SNAPSHOT, it will never offer the snapshot. Perhaps it just needs to offer both and we figure out manually which to pick.
Comment From: snicoll
Shouldn't moveToSnapshot have a special case for this rather? I don't know enough of the code to know for sure but its scope looks more limited than bomrUpgrade.
Comment From: wilkinsona
This is surprisingly complicated. When we're upgrading to new releases, x.y.z, x.y.z-Mn, and x.y.z-RCn should be considered to be newer than x.y.z-SNAPSHOT. When we're moving to snapshots it depends what the current version is. If the current version is x.y.z then x.y.z-SNAPSHOT is older. However, if the current version is x.y.z-Mn or x.y.z-RCn then x.y.z-SNAPSHOT is newer.