Skip to content

ci: release the jar when a tag is pushed - #22

Merged
floriankraemer merged 1 commit into
mainfrom
ci/release-workflow
Nov 13, 2026
Merged

floriankraemer merged 1 commit into
mainfrom
ci/release-workflow

Conversation

@floriankraemer

Copy link
Copy Markdown
Owner

Summary

  • New release.yml: on a tag push it sets the Maven version from the tag, runs ./mvnw verify, checks that --version prints the tag, and creates a draft GitHub release with cognitive-analysis.jar and generated notes (same mechanism as the PHP tool).
  • --version now prints the build version (was hard-coded 0.0.1). BuildInfo holds the lookup the SARIF report already used.
  • pom version 1.0.0-SNAPSHOT.
  • tests.yml: checkout v7, setup-java v6, upload-artifact v7, ubuntu-24.04.
  • README: download from the latest release.

Test plan

  • ./mvnw verify green (tests, JaCoCo gate, PIT)
  • New BuildInfoTest: filtered version, missing and placeholder values, --version output
  • Local dry run of the version step: versions:set -DnewVersion=1.0.0 then the jar prints cognitive-analysis 1.0.0

- Add a tag-triggered workflow that injects the version from the tag,
  runs the full build, checks --version and creates a draft release
  with the jar, like the PHP release workflow.
- Print the build version for --version instead of a hard-coded 0.0.1,
  reusing the build properties the SARIF report already read.
- Update GitHub Actions to the Node.js 24 versions and pin the runner.
- Document the release download in the README.
@floriankraemer
floriankraemer merged commit d4d8225 into main Nov 13, 2026
1 check passed
@floriankraemer
floriankraemer deleted the ci/release-workflow branch November 13, 2026 08:31
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.

1 participant