Skip to content

Latest commit

 

History

History
87 lines (64 loc) · 2.31 KB

RELEASING.md

File metadata and controls

87 lines (64 loc) · 2.31 KB

Releasing

The deployment process of cucumber-jvm is based on Deploying to OSSRH with Apache Maven.

Check Build Status

Is the build passing?

git checkout master

Also check if you can upgrade any dependencies:

make update-dependency-versions

Make the release

Remove the empty sections in the changelog. Don't commit these but run:

make release

Last bits

Wait for the release to show up on maven central. Then update the dependency in example projects:

Update the cucumber-jvm version in the documentation project:

The cucumber-jvm version for the docs is specified in the docs versions.yaml

All done! Hurray!

GPG Keys

To make a release you must have the devs@cucumber.io GPG private key imported in gpg2.

gpg --import devs-cucumber.io.key

Additionally upload privileges to the Sonatype repositories are required. See the OSSRH Guide for instructions. Then an administrator will have to grant you access to the cucumber repository.

Finally both your OSSRH credentials and private key must be setup in your ~/.m2/settings.xml - for example:

<settings>
    <servers>
        <server>
            <id>ossrh</id>
            <username>sonatype-user-name</username>
            <password>sonatype-password</password>
        </server>
    </servers>
    <profiles>
        <profile>
            <id>ossrh</id>
            <activation>
                <activeByDefault>true</activeByDefault>
            </activation>
            <properties>
                <gpg.executable>gpg2</gpg.executable>
                <gpg.useagent>true</gpg.useagent>
            </properties>
        </profile>
        <profile>
            <id>sign-with-cucumber-key</id>
            <properties>
                <gpg.keyname>dev-cucumber.io-key-id</gpg.keyname>
            </properties>
        </profile>
    </profiles>
</settings>