typelevel / typelevel/fs2-grpc
'2.7.10' release introduces SemVer incompatible dependency version changes
Open
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 284
- Forks
- 66
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 4
Description
When we update our project to sbt-fs2-grpc:2.7.10 and use it with sbt-version-policy, we suddenly get incompatible version change errors:
[error] Incompatibilities with dependencies of grpc:1.1.0
[error] com.google.guava:guava: incompatible version change from 31.0.1-android to 32.0.1-jre (compatibility: early semantic versioning)
[error] com.google.j2objc:j2objc-annotations: incompatible version change from 1.3 to 2.8 (compatibility: early semantic versioning)
[error] io.perfmark:perfmark-api: incompatible version change from 0.25.0 to 0.26.0 (compatibility: early semantic versioning)
[error] io.grpc:grpc-context: missing dependency
[error] org.checkerframework:checker-compat-qual: missing dependency
While manageable, it is unfortunate that this error happens during patch version update of a SBT plugin.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the dependency errors with sbt-fs2-grpc:2.7.10 and sbt-version-policy, then compare the resolved dependencies with the previous plugin version. Done means the patch update no longer reports the listed incompatible or missing dependencies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100