False positive dependency error when upgrading to Scala 2.13.15 from 2.13.14

[durban]

When upgrading a cross-built project from Scala 2.13.14 to 2.13.15, there are some dependency errors reported by versionPolicyReportDependencyIssues. See for example here: https://github.com/durban/choam/actions/runs/11059425885/job/30727717814#step:24:4147

[error] Incompatibilities with dependencies of choam-skiplist:0.4.0
[error]   org.scala-js:scalajs-scalalib_2.13: incompatible version change from 2.13.14+1.16.0 to 2.13.15+1.16.0 (compatibility: strict semantic versioning)
[error] Incompatibilities with dependencies of choam-skiplist:0.4.1
[error]   org.scala-js:scalajs-scalalib_2.13: incompatible version change from 2.13.14+1.16.0 to 2.13.15+1.16.0 (compatibility: strict semantic versioning)

The error seems to be caused by org.scala-js:scalajs-scalalib_2.13, whose version is updated from 2.13.14+1.16.0 to 2.13.15+1.16.0. I believe this error is a false positive, as it's supposed to be backward compatible.

[julienrf]

Thank you @durban for reporting the issue. @sjrd Could you please explain the versioning of Scala.js?

[sjrd]

I think this is the best explanation: https://github.com/scala-js/scala-js/pull/4913#issuecomment-1806257781

[julienrf]

Thank you for the pointer. What would you recommend to do in sbt-version-policy?

[sjrd]

This should be considered a compatible change, in this case.

That said, it may not be true for all libraries that have a version looking like that, so... I don't know what's best in general.