Skip to content

Conversation

@thebehera
Copy link
Contributor

Summary

  • Fix version mismatch by calculating version BEFORE publishing rather than after
  • Add check-release job to skip releases for non-code changes
  • Support both skip-release label and automatic detection of non-code files

Changes

  1. Version calculation fix: Version is now calculated once before any publishing step and reused for tagging, ensuring the tag matches the published version

  2. Skip-release mechanism:

    • Manually: Add skip-release label to any PR
    • Automatic: Detects when only non-code files changed (.github/*, *.md, .gitignore, etc.)

Test plan

  • Merge a code change PR and verify version matches in tag and Maven Central
  • Add skip-release label to a PR and verify no release is created
  • Merge a docs-only PR and verify no release is created

The version was being calculated after publishing, causing it to fetch
the just-published version from Maven Central and increment it again.

Now the version is calculated BEFORE publishing and reused for tagging.
- Add check-release job that runs before macos build
- Skip release if PR has 'skip-release' label
- Auto-detect non-code changes (.github/*, *.md, .gitignore, etc.)
- Only proceed with release when actual code files are changed
@thebehera thebehera added the skip-release Skip the deployment to maven central label Dec 20, 2025
@thebehera thebehera merged commit cf29613 into main Dec 20, 2025
4 checks passed
@thebehera thebehera deleted the fix/release-tag-version-mismatch branch December 20, 2025 01:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip-release Skip the deployment to maven central

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants