Skip to content

feat: add release-version and development-version overrides to release workflow - #8

Merged
dkropachev merged 1 commit into
masterfrom
feat/release-version-override
Apr 1, 2026
Merged

feat: add release-version and development-version overrides to release workflow#8
dkropachev merged 1 commit into
masterfrom
feat/release-version-override

Conversation

@nikagra

@nikagra nikagra commented Apr 1, 2026

Copy link
Copy Markdown

Summary

Adds two optional inputs to the Release workflow to eliminate the need for manual version-bump PRs before releasing.

Problem

Previously, to release e.g. 0.14.0.0 from a 0.13.0.1-SNAPSHOT codebase, you had to open a separate PR bumping all 7 pom.xml files to 0.14.0.0-SNAPSHOT first, wait for it to merge, then trigger the Release workflow. There was no way to specify the release version at trigger time.

Solution

  • release-version — specify the exact version to release (e.g. 0.14.0.0). Without this, Maven defaults to stripping -SNAPSHOT from the current version.
  • development-version — specify the next SNAPSHOT version after the release (e.g. 0.15.0.0-SNAPSHOT). Without this, Maven auto-increments the last digit (e.g. 0.14.0.1-SNAPSHOT).

New release flow for 0.14.0.0

Trigger the Release workflow with:

  • release-version: 0.14.0.0
  • development-version: 0.14.0.1-SNAPSHOT (or leave blank to auto-increment)

No manual pom.xml changes required.

Changes

  • Makefile: release-prepare target now reads RELEASE_VERSION and RELEASE_DEVELOPMENT_VERSION env vars and passes them as -DreleaseVersion / -DdevelopmentVersion to mvn release:prepare when set. Also fixes skip-tests handling so it applies to release:prepare (not just release:perform).
  • .github/workflows/release.yml: adds release-version and development-version inputs, passes them as env vars to the Prepare release step.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR enhances the repository’s release automation by allowing callers of the GitHub Actions Release workflow to override the Maven release and next development versions at trigger time, reducing the need for separate version-bump PRs.

Changes:

  • Add release-version and development-version optional inputs to the Release workflow and pass them into the release preparation step.
  • Update release-prepare in the Makefile to optionally pass -DreleaseVersion and -DdevelopmentVersion to mvn release:prepare.
  • Extend the release preparation step to optionally skip tests during release:prepare.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File Description
Makefile Adds env-driven flags for Maven release:prepare (release/development version overrides and skip-tests handling).
.github/workflows/release.yml Introduces new workflow_dispatch inputs and wires them into the Prepare release step via env vars.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread Makefile Outdated
Comment thread Makefile Outdated
@nikagra
nikagra force-pushed the feat/release-version-override branch from f143ab6 to c7093ae Compare April 1, 2026 14:07
Comment thread .github/workflows/release.yml Outdated
Comment thread Makefile Outdated
@nikagra
nikagra force-pushed the feat/release-version-override branch from c7093ae to e202cfb Compare April 1, 2026 16:07
@nikagra
nikagra requested a review from dkropachev April 1, 2026 16:29
@dkropachev
dkropachev merged commit 2b69321 into master Apr 1, 2026
1 check passed
@dkropachev
dkropachev deleted the feat/release-version-override branch April 1, 2026 16:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants