chore

Author: gesellix

README.md

@@ -1,3 +1,6 @@
+[![Build Status](https://img.shields.io/github/workflow/status/docker-client/docker-compose-v3/Publish?style=for-the-badge)](https://github.com/docker-client/docker-compose-v3/actions)
+[![Maven Central](https://img.shields.io/maven-central/v/de.gesellix/docker-compose.svg?style=for-the-badge&maxAge=86400)](https://search.maven.org/search?q=g:de.gesellix%20AND%20a:docker-compose)
+
 # docker-compose-v3
 
 ### About
@@ -19,4 +22,8 @@ You can find a real life example at the [Docker Client's DeployConfigReader](htt
 
 ### Contributing
 
-Feel free to submit an issue if you'd like to ask a question or propose a new feature (maybe Compose v2 support?). Pull Requests are welcome, too!
+Please submit an issue if you'd like to ask a question or propose a new feature (maybe Compose v2 support?). Pull Requests are welcome, too!
+
+## Publishing/Release Workflow
+
+See RELEASE.md

RELEASE.md

@@ -0,0 +1,15 @@
+## Publishing
+
+Packages are automatically published from the `main` branch to the GitHub Package Registry.
+Manually cut releases will be published to both GitHub Package Registry and Maven Central.
+
+## Release Workflow
+
+There are multiple GitHub Action Workflows for the different steps in the package's lifecycle:
+
+- CI: Builds and checks incoming changes on a pull request
+  - triggered on every push to a non-default branch
+- CD: Publishes the Gradle artifacts to GitHub Package Registry
+  - triggered only on pushes to the default branch
+- Release: Publishes Gradle artifacts to Sonatype and releases them to Maven Central
+  - triggered on a published GitHub release using the underlying tag as artifact version, e.g. via `git tag -m "$MESSAGE" v$(date +"%Y-%m-%dT%H-%M-%S")`