The deployment process of cucumber-jvm
is based on
Deploying to OSSRH with Apache Maven.
Is the build passing?
git checkout main
Also check if you can upgrade any dependencies:
make update-dependency-versions
Versions follow Semantic Versioning. To sum it up, it depends on what's changed (see CHANGELOG.md
). Given a version number MAJOR.MINOR.PATCH:
- Bump
MAJOR
when you make incompatible API changes:- There are
Removed
entries, orChanged
entries breaking compatibility - A cucumber library dependency upgrade was major
- There are
- Bump
MINOR
when you add functionality in a backwards compatible manner:- There are
Added
entries,Changed
entries preserving compatibility, orDeprecated
entries
- There are
- Bump
PATCH
when you make backwards compatible bug fixes:- There are
Fixed
entries
- There are
Display future version by running:
make version
Check if branch name and version are as expected. To change version run:
mvn versions:set -DnewVersion=X.Y.Z-SNAPSHOT
Secrets are required to make releases. Members of the core team can install
keybase and join the cucumberbdd
team to access these secrets.
During the release process, secrets are fetched from keybase and used to sign and upload the maven artifacts.
Check if branch name and version are as expected:
make version
Do the release:
make release
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!