Backmerge pull request #109 from Zeplinko/promote-to-stable-version

[ShivamNagpal]

Summary by CodeRabbit

• Chores
  • Updated build infrastructure and tooling configuration
  • Bumped patch version to 1.3.1
  • Updated build dependencies

[coderabbitai]

Walkthrough

This PR adds a Makefile with build and test convenience targets that wrap Maven execution, and updates the project version from 1.3.0 to 1.3.1 while upgrading the central publishing Maven plugin from 0.4.0 to 0.9.0.

Changes

Cohort / File(s)	Summary
Build Targets Makefile	New file defining two phony targets: build (executes Maven clean, spotless:apply, and package goals) and test (executes Maven test goal)
Version Updates pom.xml	Project version bumped from 1.3.0 to 1.3.1; central publishing Maven plugin upgraded from 0.4.0 to 0.9.0

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

• Verify the Makefile targets execute the intended Maven goals without errors
• Confirm the plugin version upgrade (0.4.0 → 0.9.0) is compatible and intentional

Possibly related PRs

• Release Backmerge #96: Bumps pom.xml version in a prior release cycle (1.3.0-BETA2 → 1.3.0); related through version management pattern
• Promote to beta #89: Updates project version during earlier release (1.2.0 → 1.3.0-BETA2); follows same version-bump workflow
• Promote to stable 1.3.0 #92: Advances version from 1.3.0-BETA2 → 1.3.0; precursor to this patch-level increment

Suggested reviewers

• zeplinko-bot
• astha-singh-dev

Poem

🐰 A Makefile appears with targets so clean,
Build and test now easier to convene!
Version bumps and plugins refined,
Rabbit's helpers, organized and aligned! 🏗️✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately reflects the PR's purpose as a backmerge from a release branch to develop, with reference to the source PR promoting to stable version.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch release

---

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.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

Makefile (1)

1-7: Makefile is well-structured; optional: consider adding conventional targets.

The Makefile correctly wraps Maven operations using the Maven wrapper for reproducible builds. The static analysis flags missing all and clean targets; while not critical (since Maven handles cleanup separately), you may optionally add these for convention:

• all: typically an alias to build
• clean: wraps ./mvnw clean

These are optional enhancements and can be deferred.

If you'd like to add them:

.PHONY: all build test clean

all: build

build:
	@./mvnw clean spotless:apply package

test:
	@./mvnw test

clean:
	@./mvnw clean

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 38087a1 and 9cb3b9f.

📒 Files selected for processing (2)

• Makefile (1 hunks)
• pom.xml (2 hunks)

🧰 Additional context used

🪛 checkmake (0.2.2)

Makefile

[warning] 1-1: Missing required phony target "all"

(minphony)

---

[warning] 1-1: Missing required phony target "clean"

(minphony)

🔇 Additional comments (2)

pom.xml (2)

9-9: Version bump to 1.3.1 is appropriate.

The patch version increment aligns with backmerging changes from the release branch.

---

45-45: No breaking changes documented for central-publishing-maven-plugin 0.9.0; upgrade is safe.

Version 0.9.0 introduces no breaking changes, only new features like improved skipPublishing application per module and proxy support. Your existing configuration (autoPublish, deploymentName, publishingServerId, tokenAuth) remains valid. Consider running a build test to confirm functionality in your environment.