Merge branch 'release-v1.2.x' into release-v2.2.x

Author: damianmalczewski

README.md

@@ -1,7 +1,7 @@
 # Problem4J Spring
 
 [![Build Status](https://github.com/problem4j/problem4j-spring/actions/workflows/gradle-build.yml/badge.svg)](https://github.com/problem4j/problem4j-spring/actions/workflows/gradle-build.yml)
-[![Sonatype](https://img.shields.io/maven-central/v/io.github.problem4j/problem4j-spring-bom)][maven-central]
+[![Sonatype](https://img.shields.io/maven-central/v/io.github.problem4j/problem4j-spring-bom?filter=2.2.*)][maven-central]
 [![License](https://img.shields.io/github/license/problem4j/problem4j-spring)](https://github.com/problem4j/problem4j-spring/blob/main/LICENSE)
 
 Designing clear and consistent error responses in a REST API is often harder than it looks. Without a shared standard,

RELEASING.md

@@ -41,7 +41,7 @@ issue is critical or a change can be backported with minimal effort.
 ## Maven Central
 
 [![Publish Release Status](https://github.com/problem4j/problem4j-spring/actions/workflows/gradle-publish-release.yml/badge.svg)][gradle-publish-release]
-[![Sonatype](https://img.shields.io/maven-central/v/io.github.problem4j/problem4j-spring-bom)][maven-central]
+[![Sonatype](https://img.shields.io/maven-central/v/io.github.problem4j/problem4j-spring-bom?filter=2.2.*)][maven-central]
 
 1. Keep Git tags with `vX.Y.Z-suffix` format. GitHub Actions job will only trigger on such tags and will remove `v`
    prefix.

problem4j-spring-bom/README.md

@@ -1,6 +1,6 @@
 # BOM of Problem4J
 
-[![Sonatype](https://img.shields.io/maven-central/v/io.github.problem4j/problem4j-spring-bom)](https://central.sonatype.com/artifact/io.github.problem4j/problem4j-spring-bom)
+[![Sonatype](https://img.shields.io/maven-central/v/io.github.problem4j/problem4j-spring-bom?filter=2.2.*)](https://central.sonatype.com/artifact/io.github.problem4j/problem4j-spring-bom)
 
 Bill Of Materials (BOM) for the Spring integrations of **Problem4J**, a library implementing *RFC 7807 - Problem Details
 for HTTP APIs*.