I had an open thing to check on the latest 

 references to be passed around between APIs depending on different versions of 

The semver trick refers to publishing a breaking change to a Rust library without requiring a coordinated upgrade across its downstream dependency graph.

 The trick is built around having one version of your library declare a dependency on a newer version of the same library.

Stacker Saloon

saloon

I had an open thing to check on the latest `ringrtc` release: why, if you use `jni-sys@v0.3.1`, it also gets `jni-sys@v0.4.0`.

From [`jni-sys@v0.3.1`](https://github.com/jni-rs/jni-sys/releases/tag/v0.3.1):

> This release applies the [semver trick](https://github.com/dtolnay/semver-trick) to re-export compatible types from `jni-sys 0.4` (namely `jobject`) to make it easier for `jobject` references to be passed around between APIs depending on different versions of `jni-sys`

From [semver-trick](https://github.com/dtolnay/semver-trick):

> **The semver trick refers to publishing a breaking change to a Rust library without requiring a coordinated upgrade across its downstream dependency graph.** The trick is built around having one version of your library declare a dependency on a newer version of the same library.

![](https://m.stacker.news/140545)