[DSD-9870] inji-verify 0.17.0 release

[Prafulrakhade]

Summary by CodeRabbit

• Chores
  • Stable release 1.7.0 is now available.
  • Project artifacts and sample app dependencies updated to 1.7.0.
  • Build and archive metadata (release/jar manifest versions) updated to reflect 1.7.0.

[coderabbitai]

Walkthrough

This PR updates published version strings from SNAPSHOT to release versions across build/publish metadata: vcverifier-aar and vcverifier-jar set to 1.7.0; manifest and archive versions updated to 1.7.0; a sample app dependency updated from 1.5.0-SNAPSHOT to 1.5.0. No logic changes.

Changes

Cohort / File(s)	Summary
Publish configuration vc-verifier/kotlin/vcverifier/publish-artifact.gradle	Updated MavenPublication version properties: vcverifier-aar and vcverifier-jar from 1.7.0-SNAPSHOT → 1.7.0.
Build metadata vc-verifier/kotlin/vcverifier/build.gradle.kts	Updated Jar manifest Implementation-Version and archiveVersion to 1.7.0 (from snapshot values).
Sample app dependency vc-verifier/kotlin/sample-java-app/pom.xml	Updated dependency vcverifier-jar from 1.5.0-SNAPSHOT → 1.5.0.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• [INJIVER-1369]: updated the artifact version #220: Changes the same MavenPublication version properties in vc-verifier/kotlin/vcverifier/publish-artifact.gradle.

Suggested reviewers

• mayuradesh

Poem

🐰 Hopped from snapshot to release, neat and slow,
Numbers trimmed and ready — 1.7.0.
Manifests polished, dependencies aligned,
A little carrot cheer for the build pipeline. 🥕

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The PR title references version 0.17.0 but the actual changes update versions to 1.7.0, creating a significant discrepancy between the title and the actual changeset.	Correct the PR title to accurately reflect the version being released, e.g., '[DSD-9870] inji-verify 1.7.0 release' instead of 0.17.0.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@vc-verifier/kotlin/vcverifier/publish-artifact.gradle`:
- Line 99: The publication blocks that hardcode version = "1.7.0" must be
unified with the jarRelease task metadata to avoid version drift: introduce a
single releaseVersion value (e.g., val releaseVersion =
(findProperty("VCVERIFIER_VERSION") ?: project.version).toString()) and use that
variable everywhere — replace the hardcoded publication version values in the
publish-artifact.gradle publication blocks with releaseVersion and update the
jarRelease task (manifest attribute "Implementation-Version" and
archiveVersion.set(...)) to also use releaseVersion so the published artifact
and its embedded metadata match.

---

ℹ️ Review info

Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 3f5f5e17-e271-4cac-8f46-189aa4efce18

📥 Commits

Reviewing files that changed from the base of the PR and between 723c66a and 8d6da5a.

📒 Files selected for processing (1)

• vc-verifier/kotlin/vcverifier/publish-artifact.gradle

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@vc-verifier/kotlin/sample-java-app/pom.xml`:
- Line 54: The sample app's pom dependency for artifactId "vcverifier-jar" is
pinned to version 1.5.0; update the <version> element in the sample project's
pom.xml to 1.7.0 so the sample uses the same release as declared in
vc-verifier/kotlin/vcverifier/build.gradle.kts, ensuring the sample exercises
the published artifact.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 8b2f03bc-949d-473e-a36a-989c995633f3

📥 Commits

Reviewing files that changed from the base of the PR and between 8d6da5a and 25da06b.

📒 Files selected for processing (2)

• vc-verifier/kotlin/sample-java-app/pom.xml
• vc-verifier/kotlin/vcverifier/build.gradle.kts