v4.0.7

Release run: #1

What's Changed

• Adopt GHA Scala Library Release Workflow by @rtyley in #299

Full Changelog: v4.0.6...v4.0.7

v4.0.6

The rollout of this release to the 7 apps that use this library met unexpected ☠️ fatal runtime compatibility problems ☠️ for those apps that weren't fully up to date with CAPI client libraries.

The versions of the content-api-client & content-api-models libraries resolved within those apps were actually incompatible (though it would have been hard to spot it - the incompatibility was only an upgrade of content-api-models v17.5.1 → v17.5.2 - fairly subtle). See issue #301 for more details.

This kind of incompatibility is unpredictable 🎲 and unfortunately very hard to write tests for - more unit tests was not the answer to stopping this happening again.

This ultimately led into the work in gha-scala-library-release-workflow, that includes using sbt-version-policy to set versionScheme to early-semver, and use the releaseVersion setting to get correct version number bumps by using automated compatibility testing:

releaseVersion := ReleaseVersion.fromAggregatedAssessedCompatibilityWithLatestRelease().value

With all these libraries updated to use gha-scala-library-release-workflow, and all of them updated to use versions that are using early-semver, this kind of rollout problem should hopefully be eliminated for subsequent releases. ✨ ✨ ✨

What's Changed

• chore(deps): Non-AWS dependency updates by @gu-scala-steward-public-repos in #289
• chore(deps): AWS dependency updates by @gu-scala-steward-public-repos in #288
• Drop support for no-longer-used Play version v2.6 by @rtyley in #291
• Modernise GitHub Action for CI by @rtyley in #293
• Drop Specs2, consolidate on ScalaTest by @rtyley in #292
• chore(deps): AWS dependency updates by @gu-scala-steward-public-repos in #294
• Dependency updates by @rtyley in #295
• chore(deps): AWS dependency updates by @gu-scala-steward-public-repos in #296

New Contributors

• @gu-scala-steward-public-repos made their first contribution in #289

Full Changelog: v4.0.5...v4.0.6

PRs updating Guardian projects to use this release

Found by using GitHub search for "fapi-client-" & "facia-json-":

• guardian/ophan#5540
• guardian/frontend#26578
• guardian/apple-news#263
• guardian/editors-picks-uploader#20
• guardian/story-packages#184 - caused issues, see guardian/story-packages#186
• guardian/facia-tool#1526 - caused issues, see guardian/facia-tool#1526 (comment)
• guardian/mobile-apps-api#2699

Update SpecialReportAlt tag

Update CAPI client version to use updated SpecialReportAlt tag: guardian/content-api-scala-client#380

v4.0.3

What's Changed

• adds specialReport palette to fronts by @dskamiotis in #281
• Add SpecialReportAlt to CardStyle by @DanielCliftonGuardian in #280

New Contributors

• @DanielCliftonGuardian made their first contribution in #280

Full Changelog: v4.0.2...v4.0.3

v4.0.2

What's Changed

• Integrate repo with snyk GHA by @NovemberTang in #274
• Prioritise replacement images over cutouts by @jonathonherbert in #278

New Contributors

• @NovemberTang made their first contribution in #274

Full Changelog: v4.0.1...v4.0.2

v4.0.1

What's Changed

• Compile against v19.0.3 of the CAPI client by @rtyley in #276
• Switch from manual CHANGELOG.md to GitHub Releases by @rtyley in #275

Full Changelog: v4.0.0...v4.0.1

v4.0.0 - for CAPI client v19 or later

What's Changed

This new release depends on CAPI client v19, which is binary-incompatible with previous releases of the CAPI client. When you update to this release of the FAPI client, you will need to ensure you are using code that has been compiled against CAPI client v19 or later - otherwise you may see a java.lang.NoSuchMethodError exception.

• Add Continuous Integration (CI) as GitHub Action by @rtyley in #272
• Compile against v19 of the CAPI client (incompatible with versions prior to v19) by @rtyley in #271

Full Changelog: v3.3.13...v4.0.0

Testing sbt updates from PR #269

Just wanted to check that #269 hadn't broken the release process. Everything seemed to work fine!

2.6.1 <Botched release>

This was Phil trying (and failing) to publish this change. The release process failed part of the way through. Sad times.