Skip to content

chore: bump to next development version#381

Merged
soul2zimate merged 1 commit intomainfrom
chore/bump-version
Mar 27, 2026
Merged

chore: bump to next development version#381
soul2zimate merged 1 commit intomainfrom
chore/bump-version

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

This PR updates the project to the next development version after the release.

Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@github-actions github-actions bot force-pushed the chore/bump-version branch from 25f7675 to 6c24928 Compare March 27, 2026 08:02
@soul2zimate soul2zimate reopened this Mar 27, 2026
@qodo-code-review
Copy link
Copy Markdown
Contributor

Review Summary by Qodo

Bump project version to 0.0.15-SNAPSHOT

📦 Other

Grey Divider

Walkthroughs

Description
• Update project version from 0.0.14-SNAPSHOT to 0.0.15-SNAPSHOT
• Prepare development branch for next release cycle
Diagram
flowchart LR
  A["Current Version<br/>0.0.14-SNAPSHOT"] -- "Version Bump" --> B["Next Dev Version<br/>0.0.15-SNAPSHOT"]
Loading

Grey Divider

File Changes

1. pom.xml ⚙️ Configuration changes +1/-1

Update Maven project version number

• Updated project version from 0.0.14-SNAPSHOT to 0.0.15-SNAPSHOT
• Prepares Maven project for next development iteration

pom.xml


Grey Divider

Qodo Logo

@qodo-code-review
Copy link
Copy Markdown
Contributor

qodo-code-review bot commented Mar 27, 2026

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📎 Requirement gaps (0) 📐 Spec deviations (0)

Grey Divider


Remediation recommended

1. README version mismatch 🐞 Bug ⚙ Maintainability
Description
pom.xml was bumped to 0.0.15-SNAPSHOT, but README.md still instructs Maven users to depend on
0.0.9-SNAPSHOT, so users following the docs will pull an outdated (and potentially unavailable)
artifact instead of the current development version.
Code

pom.xml[8]

+  <version>0.0.15-SNAPSHOT</version>
Evidence
The project’s canonical artifact version is defined in pom.xml, but the README’s Maven dependency
snippet hardcodes a different snapshot version for the same groupId/artifactId, creating
inconsistent guidance after this bump.

pom.xml[6-9]
README.md[103-109]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The project version was bumped to `0.0.15-SNAPSHOT`, but the README’s Maven dependency example still uses `0.0.9-SNAPSHOT`, which will mislead users into using an outdated version.

### Issue Context
The README appears to provide copy/paste dependency coordinates for `io.github.guacsec:trustify-da-java-client`.

### Fix Focus Areas
- README.md[98-110]
- pom.xml[6-9]

### Suggested change
Update the README Maven dependency snippet to either:
- use the new development version `0.0.15-SNAPSHOT`, or
- avoid hardcoding by using a placeholder/instruction to use the latest published version.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


Grey Divider

ⓘ The new review experience is currently in Beta. Learn more

Grey Divider

Qodo Logo

@soul2zimate soul2zimate enabled auto-merge (squash) March 27, 2026 08:35
@github-actions
Copy link
Copy Markdown
Contributor Author

Test Results

379 tests   379 ✅  2m 0s ⏱️
 25 suites    0 💤
 25 files      0 ❌

Results for commit 6c24928.

@soul2zimate soul2zimate merged commit d955d8e into main Mar 27, 2026
32 of 41 checks passed
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