new_release.yml

name: New release request
description: Will be created by the author of the plugin, so not relevant for the public :-)
labels: [ ]
assignees: [ ]
body:
    - type: textarea
      id: describe-the-release
      attributes:
          label: Describe the release details (required)
          description: |
              Just submit this as new issue...
          value: |
              This is the place holder to release the new **6.0.0** 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%3A6.0.0).

              # Release-Guide
              see
              - https://central.sonatype.org/publish/publish-guide
              - https://central.sonatype.org/publish/publish-portal-maven/
              - (OSSRH was deprecated on June 30, 2025 -- http://central.sonatype.org/pages/ossrh-guide.html)
              
              The release process has changed from the old OSSRH staging to the new Central Portal:
              - Option 1: Use the new central-publishing-maven-plugin (recommended for automated releases)
              - Option 2: Use the OSSRH Staging API Service (compatibility layer)

              - [ ] verify that `~/.m2/settings.xml` exists (https://central.sonatype.org/publish/publish-portal-maven/#credentials)
                    - contains user token credentials from https://central.sonatype.com/ (generate token at https://central.sonatype.org/publish/generate-portal-token/)
              - [ ] Set release version: `bump2version patch --dry-run --verbose`
              - [ ] Push changes and tag: `git push origin master --follow-tags`
              - [ ] wait for github actions to pass
              - [ ] `mvn clean deploy -Pgpg`
              - [ ] verify plugin is available on (might take some time) https://repo1.maven.org/maven2/io/github/git-commit-id/git-commit-id-plugin-core/
              - [ ] Set next development version: `bump2version patch --dry-run --verbose`
              - [ ] Push snapshot version: `git push origin master`
              - [ ] under [Milestones](https://github.com/git-commit-id/git-commit-id-plugin-core/milestones) close old milestone
              - [ ] under [Milestones](https://github.com/git-commit-id/git-commit-id-plugin-core/milestones) create new milestone for new version
              - [ ] under [Releases](https://github.com/git-commit-id/git-commit-id-plugin-core/releases) publish Release-Notes
              - [ ] update readme to point to the latest version available
      validations:
          required: true