JNG-6022 [Release] Updating versions

[robertcsakany]

No description provided.

[coderabbitai]

Walkthrough

This pull request updates various dependency version numbers in the pom.xml file. The changes adjust timestamps and commit identifiers, with some dependencies now incorporating a feature identifier for marking selected range items in HTTP headers. No changes were made to the overall structure of the file.

Changes

File

Change Summary

pom.xml

Updated dependency versions: - judo-meta-rdbms-version: from 1.0.2.20250221_042046_220587b1_develop to 1.0.2.20241202_042200_e7bf5d81_develop - judo-meta-ui-version: updated timestamp to 20250131_191056_484ccd59_develop - judo-meta-psm-version: updated to 1.3.0.20241202_042213_d30645b4_develop - judo-meta-asm/version, judo-meta-expression/version, judo-meta-liquibase/version, judo-tatami-core-version: similar timestamp updates - judo-dao-api, judo-sdk-common, judo-operation-utils, judo-runtime-core, judo-tatami-base: versions now include feature_JNG_6022_markSelectedRangeItemsInHttpHeader

Poem

I'm a little rabbit with a curious hop,
I saw the versions change, then didn't stop!
From timestamps of old to freshly spun dates,
Each dependency now hops at updated rates.
With a twitch of my ears, I cheer this update,
Leaping into code with a joyful gait!
🐇✨

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

‼️ IMPORTANT
Auto-reply has been disabled for this repository in the CodeRabbit settings. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

pom.xml (1)

68-82: Review Timestamp Consistency Across Versions
There is a noticeable variation in the timestamp portions of the version strings. For example, some dependencies are updated with a December 2024 date (e.g., 20241202, 20241213) while several feature-flagged dependencies use a February 2025 date (e.g., 20250219) and one (judo-meta-ui) uses 20250131. Please verify that these differences are intentional and consistent with your versioning policy, ensuring that they do not lead to dependency mismatches in downstream projects.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e8c34e8 and 6c2a52a.

📒 Files selected for processing (1)

• pom.xml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: ⏳ Build, test and deploy artifacts

🔇 Additional comments (2)

pom.xml (2)

68-68: Metadata Dependency Version Updates Verified
The version updates for metadata dependencies—specifically for <judo-meta-rdbms-version>, <judo-meta-ui-version>, <judo-meta-psm-version>, <judo-meta-asm-version>, <judo-meta-expression-version>, and <judo-meta-liquibase-version>—have been updated as intended. Please verify that these new version strings (with December 2024 dates for most elements except the UI version) align with your release strategy and that any downstream dependencies expecting these updates are adjusted accordingly.

Also applies to: 70-74

---

75-76: Feature Identifier Dependency Versions for JNG-6022
The dependencies <judo-dao-api-version>, <judo-sdk-common-version>, <judo-operation-utils-version>, <judo-runtime-core-version>, <judo-tatami-base-version>, and <judo-tatami-core-version> now include the feature identifier feature_JNG_6022_markSelectedRangeItemsInHttpHeader. This update appears to be in line with the release objectives. Please confirm that all related modules and dependency resolution mechanisms have been updated to use these new version strings.

Also applies to: 78-78, 80-82