# Dependency locking picking up non-release versions

**URL:** <https://discuss.gradle.org/t/dependency-locking-picking-up-non-release-versions/29111>\
**Category:** Help/Discuss\
**Created:** [October 17, 2018, 2:20pm UTC](https://discuss.gradle.org/t/dependency-locking-picking-up-non-release-versions/29111 "2018-10-17T14:20:36Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![lukasz.sanek](https://avatars.discourse-cdn.com/v4/letter/l/ce7236/32.png) [@lukasz.sanek](https://discuss.gradle.org/u/lukasz.sanek)\
**Post date:** [October 17, 2018, 2:20pm UTC](https://discuss.gradle.org/t/dependency-locking-picking-up-non-release-versions/29111/1 "2018-10-17T14:20:36Z")

</div>

Hi, we’re using Gradle’s dependency locking and noticed an unexpected behavior with some of the dependencies. An example of a problematic dependency is [https://mvnrepository.com/artifact/org.scalatest/scalatest\_2.12/3.0.6-SNAP3](https://mvnrepository.com/artifact/org.scalatest/scalatest_2.12/3.0.6-SNAP3) - what’s happening is that the declared dynamic version of that dependency in our build file is `3.0.+`, however the dependency locking mechanism picks up `3.0.6-SNAP3` as the latest version instead of `3.0.5`. Is that intentional? Shouldn’t it only consider release versions (i.e., without any metadata or suffixes)?