Enable automatic release publishing and fix release workflow for pre-releases

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Minor - P4
    • 1.0.0
    • Affects Version/s: None
    • Component/s: Build
    • None
    • 1
    • None
    • Not Needed
    • None
    • None
    • None
    • None
    • None
    • None

      Complete the release automation so the next alpha can be cut end-to-end. Three pieces of work:

      1. Auto-publishing: change the release task in publish.sh from closeSonatypeStagingRepository to closeAndReleaseSonatypeStagingRepository so a release is published to Maven Central automatically rather than requiring a manual release step. Addresses the source notes tagged TODO-HIBERNATE-128.

      2. Release-workflow versioning: the GitHub release.yml workflow assumes the development snapshot in gradle.properties is X.Y.Z-SNAPSHOT, with the pre-release counter living only in the release input and git tag (as in mongo-java-driver). gradle.properties instead held 1.0.0-alpha1-SNAPSHOT, which fails the snapshot-version check when releasing a pre-release. Change it to 1.0.0-SNAPSHOT to match the workflow's convention.

      3. Release title: the drafted GitHub release used the title "Java Driver <version>" (copied from mongo-java-driver). Correct it to "MongoDB Extension for Hibernate ORM <version>".

            Assignee:
            Jeffrey Yemin
            Reporter:
            Ross Lawley
            Slav Babanin
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: