Add documentation for maven-central

Author: LogFlames

sbom-github.md

@@ -61,6 +61,22 @@ By the end of this post, you will clearly understand how to add SBOMs to your so
 3. Make a release  :)
    The final result looks like this: https://github.com/chains-project/maven-lockfile/releases/tag/v3.0.0
 
+## Maven Central
+
+JReleaser can also upload the SBOMs to Maven Central from version 1.6.0. If running JReleaser locally, make sure to use atleast version 1.6.0 and the SBOMs generated by `cyclonedx-maven-plugin` will be uploaded to Maven Central. If using the `jreleaser/release-action` action, be aware that even if you use the latest version of the action it can pull different versions of JReleaser. If using atleast version 1.6.0 it will upload the SBOMs to Maven Central.
+
+```yml
+  - name: Run JReleaser
+    uses: jreleaser/release-action@f69e545b05f149483cecb2fb81866247992694b8
+    with:
+      version: 1.15.0
+      arguments: full-release 
+    env:
+      JRELEASER_GITHUB_TOKEN: ${{ secrets.JRELEASER_GITHUB_TOKEN }}
+      [...]
+```
+
+The final result looks like this: https://repo1.maven.org/maven2/io/github/chains-project/maven-lockfile/5.3.5/
+
 ## Conclusion
 In conclusion, adding SBOMs to your GitHub releases is a simple and effective way to improve the security and integrity of your software products. Following the steps outlined in this blog post, you can easily generate and add an SBOM to your GitHub release using Maven and JReleaser. With an SBOM, you can identify and remediate vulnerabilities in your software products on time, reducing the risk of security breaches and ensuring the trust of your users. We hope this post has helped guide you through adding SBOMs to your GitHub releases, and we encourage you to continue exploring ways to improve the security and quality of your software products.
-