Release 6.0.0

[TheSnoozer]

This is the place holder to release the new 6.0.0 version.
Previous releases can be found under https://repo1.maven.org/maven2/io/github/git-commit-id/git-commit-id-plugin-core/

Note that the current open tickets should be addressed, before performing a release.

General scope of the new release:

Fixed some minor things, added some minor features...(full list https://github.com/git-commit-id/git-commit-id-plugin-core//issues?q=milestone%3A6.0.0-rc.2).

Release-Guide

see http://central.sonatype.org/pages/ossrh-guide.html

• verify that ~/.m2/settings.xml exists and contains username/password which is required as per https://central.sonatype.org/publish/publish-maven/#distribution-management-and-authentication
• update dependencies mvn versions:display-dependency-updates
• wait for github actions to pass
• mvn release:prepare
  [INFO] Checking dependencies and plugins for snapshots ...
  What is the release version for "Git Commit Id Plugin Core"? (io.github.git-commit-id:git-commit-id-plugin-core) 6.0.0: : [ENTER]
  What is SCM release tag or label for "Git Commit Id Plugin Core"? (io.github.git-commit-id:git-commit-id-plugin-core) git-commit-id-plugin-core-6.0.0: : v6.0.0 [ENTER]
  What is the new development version for "Git Commit Id Plugin Core"? (io.github.git-commit-id:git-commit-id-plugin-core) 6.0.1-SNAPSHOT: : [ENTER]
• wait for github actions to pass
• mvn release:perform
  • (or mvn clean source:jar javadoc:jar deploy -Pgpg from the git tag)
  • (or mvn release:perform -Dresume=false)
  • Note: If the uploading of the artifacts fails, ensure that a settings.xml exists under the local .m2-Folder
• then go to https://s01.oss.sonatype.org/ log in there and go to the staging repositories, there will be the plugin, you have to first close and then release it if validation passed.
• verify plugin is available on (might take some time) https://repo1.maven.org/maven2/io/github/git-commit-id/git-commit-id-plugin-core/
• under Milestones close old milestone
• under Milestones create new milestone for new version
• under Releases publish Release-Notes
• update readme to point to the latest version available