Drop project snapshots

Author: malczuuu

.github/copilot-instructions.md

@@ -32,9 +32,7 @@
     - CI/CD via GitHub Actions:
         - `.github/workflows/gradle-build.yml` (build/test),
         - `.github/workflows/gradle-dependency-submission.yml` (dependency graph),
-        - `.github/workflows/gradle-publish-release.yml` (release),
-        - `.github/workflows/gradle-publish-snapshot.yml` (snapshot),
-        - `.github/workflows/validate-next_version.txt.yml` (next version for snapshot builds validation).
+        - `.github/workflows/gradle-publish-release.yml` (release).
     - All CI builds use JDK 17 and Gradle Wrapper.
 
 ## Project Layout & Key Files

.github/utils/README.md

@@ -72,8 +72,6 @@ higher is required to use this library.
    }
     ```
 
-For using snapshot versions [**Snapshots** chapter of `RELEASING.md`](RELEASING.md#sonatype-snapshots).
-
 ## Problem4J Links
 
 - [`problem4j-core`][problem4j-core] - Core library defining `Problem` model and `ProblemException`.
@@ -94,8 +92,14 @@ version Gradle runs on.
 ./gradlew clean build
 ```
 
+To execute tests use `test` task.
+
+```bash
+./gradlew clean test
+```
+
 To format the code according to the style defined in [`build.gradle.kts`](./build.gradle.kts) rules use `spotlessApply`
-task.
+task. **Note** that **building will fail** if code is not properly formatted.
 
 ```bash
 ./gradlew spotlessApply

.github/utils/next_version.txt

@@ -1,71 +1,16 @@
 # Releasing
 
-## Sonatype Snapshots
-
-See [`gradle-publish-snapshot.yml`](.github/workflows/gradle-publish-snapshot.yml) for publishing snapshot version
-instructions. Workflow requires manual trigger for snapshot build so it's not published regularly.
-
-Artifacts are published to Snapshot Repository, using following Gradle task.
-
-```bash
-./gradlew -Pversion=<version> publishAllPublicationsToCentralPortalSnapshots
-```
-
-### Accessing packages from Sonatype Snapshots
-
-1. Maven:
-   ```xml
-   <repositories>
-       <repository>
-           <id>sonatype-snapshots</id>
-           <url>https://central.sonatype.com/repository/maven-snapshots/</url>
-           <releases>
-               <enabled>false</enabled>
-           </releases>
-           <snapshots>
-               <enabled>true</enabled>
-               <updatePolicy>always</updatePolicy>
-           </snapshots>
-       </repository>
-   </repositories>
-   <dependencies>
-   <dependency>
-       <groupId>io.github.malczuuu.problem4j</groupId>
-       <artifactId>problem4j-core</artifactId>
-       <version>1.3.0-SNAPSHOT</version>
-   </dependency>
-   </dependencies>
-   ```
-2. Gradle (Kotlin DSL):
-   ```kotlin
-   repositories {
-       mavenCentral()
-       maven {
-           url = uri("https://central.sonatype.com/repository/maven-snapshots/")
-           content {
-               includeGroup("io.github.malczuuu.problem4j")
-           }
-           mavenContent {
-               snapshotsOnly()
-           }
-       }
-   }
-   dependencies {
-       implementation("io.github.malczuuu.problem4j:problem4j-core:1.3.0-SNAPSHOT")
-   }
-   ```
-
 ## Maven Central
 
+[![Publish Release Status](https://github.com/malczuuu/problem4j-core/actions/workflows/gradle-publish-release.yml/badge.svg)][gradle-publish-release]
+[![Sonatype](https://img.shields.io/maven-central/v/io.github.malczuuu.problem4j/problem4j-core)][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.
-2. After publishing a release, update [`next_version.txt`](.github/utils/next_version.txt) for snapshot builds
-   automation.
-3. The releasing procedure only uploads the artifacts to Sonatype repository. You need to manually log in to Sonatype to
+2. The releasing procedure only uploads the artifacts to Sonatype repository. You need to manually log in to Sonatype to
    push the artifacts to Maven Central.
 
-See [`gradle-publish-release.yml`](.github/workflows/gradle-publish-release.yml) for publishing release versions
-instructions.
+See [`gradle-publish-release.yml`][gradle-publish-release.yml] for publishing release versions instructions.
 
 Set the following environment variables in your CI/CD (GitHub Actions, etc.):
 
@@ -86,3 +31,9 @@ Artifacts are published to Maven Central via Sonatype, using following Gradle ta
 ```
 
 This command uses `nmcp` Gradle plugin - [link](https://github.com/GradleUp/nmcp).
+
+[gradle-publish-release]: https://github.com/malczuuu/problem4j-core/actions/workflows/gradle-publish-release.yml
+
+[gradle-publish-release.yml]: .github/workflows/gradle-publish-release.yml
+
+[maven-central]: https://central.sonatype.com/artifact/io.github.malczuuu.problem4j/problem4j-core