Update sbt to 1.7.1

[scala-steward]

Updates org.scala-sbt:sbt from 1.6.2 to 1.7.1.
GitHub Release Notes - Version Diff

I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.

If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.

Configure Scala Steward for your repository with a .scala-steward.conf file.

Have a fantastic day writing Scala!

Adjust future updates

Add this to your .scala-steward.conf file to ignore future updates of this dependency:

updates.ignore = [ { groupId = "org.scala-sbt", artifactId = "sbt" } ]

Or, add this to slow down future updates of this dependency:

dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "org.scala-sbt", artifactId = "sbt" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

[PawelLipski]

☹️

[LukaszKontowski]

Since sbt 1.7.0 "a concrete version such as ++ 3.0.1 requires exact version to be present in crossScalaVersion" - see release notes here: https://github.com/sbt/sbt/releases/tag/v1.7.0

[LukaszKontowski]

Current error:
[error] bad option: '-Ymacro-annotations'
is connected to the fact that when sbt "++ 2.12.13 test" is invoked - for some reason compilation starts both for scala 2.12 and for scala 2.13 - e.g. https://github.com/VirtusLab/akka-serialization-helper/runs/7319169873?check_suite_focus=true

And that's why the error occurs - it is connected to https://github.com/VirtusLab/akka-serialization-helper/blob/main/build.sbt#L116 - where after invoking sbt "++ 2.12.13 test" there are two compilations ruuning - for 2.12 and 2.13 scala versions (scalaVersionAxis.value.map gets invoked two times - one for 2.13 and one for 2.12)

And this is for sbt 1.7.x - for 1.6.x builds - sbt "++ 2.12.13 test" would invoke only one compilation for scala 2.12

[LukaszKontowski]

The solution for mentioned error ([error] bad option: '-Ymacro-annotations') is here: 20ef8e1

• checking by scalaVersionAxis.value

has been replaced by

• checking by CrossVersion.partialVersion(scalaVersion.value) (which is a recommended way when using crossScalaVersions - see https://www.scala-sbt.org/1.x/docs/Cross-Build.html#Change+settings+depending+on+the+Scala+version )

[PawelLipski]

Looks neat indeed!