From d3dbe31b175fb80884d3beec103f4b5e8a87ac56 Mon Sep 17 00:00:00 2001 From: Roberto Tyley Date: Thu, 25 Jan 2024 15:12:22 +0000 Subject: [PATCH] Prevent runtime incompatibility with 'early-semver' Now that both content-api-models and content-api-scala-client are both using 'early-semver' and adhering to it (thanks to gha-scala-library-release-workflow and sbt-version-policy) this should mean that it is **no longer possible** for a single project that depends on content-api-scala-client, content-api-models and facia-scala-client to have _incompatible_ versions of those artifacts. https://github.com/guardian/content-api-scala-client/pull/405 --- project/dependencies.scala | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/project/dependencies.scala b/project/dependencies.scala index 915cfdb1..8aeb6a3a 100644 --- a/project/dependencies.scala +++ b/project/dependencies.scala @@ -1,7 +1,7 @@ import sbt._ object Dependencies { - val capiVersion = "19.2.3" + val capiVersion = "20.0.2-PREVIEW.update-to-latest-version-of-content-api-models-scala.2024-01-25T1416.253f60e5" val awsSdk = "com.amazonaws" % "aws-java-sdk-s3" % "1.12.524" val commonsIo = "org.apache.commons" % "commons-io" % "1.3.2"