Release 9.0.1

[TheSnoozer]

Describe the release details (required)

This is the place holder to release the new 9.0.1 version.
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-maven-plugin/issues?q=milestone%3A9.0.1).

Release-Guide

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

• run an actual test with a local installed plugin (using https://github.com/git-commit-id/git-commit-id-maven-debugging)

• ensure the local maven version is 3.9.0 and newer to avoid MNG-7055

• 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

• mvn release:prepare
  [INFO] Checking dependencies and plugins for snapshots ...
  What is the release version for "Git Commit Id Maven Plugin"? (io.github.git-commit-id:git-commit-id-maven-plugin) 9.0.1: : [ENTER]
  What is SCM release tag or label for "Git Commit Id Maven Plugin"? (io.github.git-commit-id:git-commit-id-maven-plugin) git-commit-id-maven-plugin-9.0.1: : v9.0.1 [ENTER]
  What is the new development version for "Git Commit Id Maven Plugin"? (io.github.git-commit-id:git-commit-id-maven-plugin) 9.0.2-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-maven-plugin/

• 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

• run performance comparison with previous release (https://gist.github.com/TheSnoozer/7891eb9412c9584a052f00650d9c516b)

[TheSnoozer]

    [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:3.1.2:deploy (default-deploy) on project git-commit-id-maven-plugin: Failed to deploy artifacts: Could not transfer artifact io.github.git-commit-id:git-commit-id-maven-plugin:pom:9.0.1 from/to ossrh (https://s01.oss.sonatype.org/service/local/staging/deploy/maven2/): status code: 401, reason phrase: Content access is protected by token (401) -> [Help 1]
    [ERROR] 
    [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
    [ERROR] Re-run Maven using the -X switch to enable full debug logging.
    [ERROR] 
    [ERROR] For more information about the errors and possible solutions, please read the following articles:
    [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

From https://community.sonatype.com/t/401-content-access-is-protected-by-token-authentication-failure-while-performing-maven-release/12741

We’ve recently made necessary changes to our account management system that involves requiring a user token to publish. Although we attempted to reach out to all of our publishers before this change, we realize that the communication might not have reached you. Please follow the instructions on publishing via a user token in order to resolve this issue.

Please keep in mind that the user tokens generated in Central Portal cannot be used in OSSRH. Additionally, if you need to reset your OSSRH password, please follow these instructions to manage your credentials.