increase version number

[Dert1129]

Summary by CodeRabbit

• Chores
  • Version bump: Project version updated to 3.4.0 across build configurations and deployment artifacts.

[coderabbitai]

Walkthrough

The project version is bumped from 3.3.0 to 3.4.0 in two places: the Gradle version property in build.gradle and the IMAGE_TAG environment variable in the GitHub Actions CI workflow.

Changes

Version bump 3.3.0 → 3.4.0

Layer / File(s)	Summary
Gradle version and CI IMAGE_TAG bump build.gradle, .github/workflows/build-gradle-project.yml	version in build.gradle and IMAGE_TAG in the CI workflow env are both changed from 3.3.0 to 3.4.0.

Possibly related PRs

• KPMP/pegasus-data#210: Performs the same version bump pattern (3.2.0 → 3.3.0) across the same two files (build.gradle and .github/workflows/build-gradle-project.yml).

🚥 Pre-merge checks | ✅ 2

✅ Passed checks (2 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch KPMP-6721_increase-version

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 6efad27b-1c65-4d66-a341-d8ee6e4ecfba

📥 Commits

Reviewing files that changed from the base of the PR and between b6eb73d and e15264b.

📒 Files selected for processing (2)

• .github/workflows/build-gradle-project.yml
• build.gradle

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Check if gradle build output includes the docker image tag
./gradlew build docker 2>&1 | grep -i 'kingstonduo/pegasus-data'

# Check if there are any version extraction mechanisms in the workflow
grep -r "project.version\|gradle.*version\|version.txt" .github/workflows/

Repository: KPMP/pegasus-data

Length of output: 134

---

🏁 Script executed:

# Check build.gradle around line 16 for version
echo "=== build.gradle lines 1-50 ==="
head -50 build.gradle

# Check the getCurrentGitBranch function around line 89
echo "=== build.gradle lines 80-100 ==="
sed -n '80,100p' build.gradle

# Read the full workflow file
echo "=== .github/workflows/build-gradle-project.yml ===" 
cat .github/workflows/build-gradle-project.yml

Repository: KPMP/pegasus-data

Length of output: 3897

---

🏁 Script executed:

# Check if there's any mechanism to capture gradle output or image tag in workflow
grep -n "grep\|sed\|awk\|output" .github/workflows/build-gradle-project.yml

# Check if build.gradle has any output mechanism for the image tag
grep -n "println\|docker.*push\|docker.*tag\|docker.*image" build.gradle

Repository: KPMP/pegasus-data

Length of output: 454

---

Fix Docker image tag mismatch between Gradle build and workflow push on master branch.

The current setup has a critical flaw: on the master branch, Gradle builds an image named kingstonduo/pegasus-data:3.4.0 (from project.version via getCurrentGitBranch()), but the workflow attempts to push kingstonduo/pegasus-data:master (line 49). This causes the push to fail because the locally built image has a different tag.

The core issue is that IMAGE_TAG and project.version in build.gradle are hardcoded separately:

• When on develop: Both happen to be 3.4.0, so the push succeeds
• When on master: Gradle builds 3.4.0 but the workflow tries to push master — image tag mismatch

Extract the image tag dynamically from the Gradle build output instead of hardcoding IMAGE_TAG. This ensures a single source of truth for versioning across the build and deployment pipeline.