Skip to content

Conversation

techy4shri
Copy link
Contributor

@techy4shri techy4shri commented May 2, 2025

πŸ“‹ Description

JIRA ID:

Part of this issue

βœ… Type of Change

  • 🐞 Bug fix (non-breaking change which resolves an issue)
  • ✨ New feature (non-breaking change which adds functionality)
  • πŸ”₯ Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • πŸ›  Refactor (change that is neither a fix nor a new feature)
  • βš™οΈ Config change (configuration file or build script updates)
  • πŸ“š Documentation (updates to docs or readme)
  • πŸ§ͺ Tests (adding new or updating existing tests)
  • 🎨 UI/UX (changes that affect the user interface)
  • πŸš€ Performance (improves performance)
  • 🧹 Chore (miscellaneous changes that don't modify src or test files)

ℹ️ Additional Information

Summary by CodeRabbit

Summary by CodeRabbit

  • Chores
    • Updated GitHub Actions workflows to use newer versions of key actions, including upgrading Java setup steps and switching the Java distribution from 'adopt' to 'temurin'. No changes to workflow logic or user-facing features.

Copy link

coderabbitai bot commented May 2, 2025

Walkthrough

The GitHub Actions workflows for building, packaging, and static analysis were updated to use newer versions of the setup-java action, moving from version 2 to version 4. Additionally, the Java distribution was switched from 'adopt' to 'temurin' across all workflows. The checkout action in the packaging workflow was also updated from version 2 to version 3. No changes were made to the overall workflow logic or steps beyond these version and configuration updates.

Changes

File(s) Change Summary
.github/workflows/build-on-pull-request.yml Updated setup-java action from v2 to v4; changed Java distribution from 'adopt' to 'temurin'.
.github/workflows/package.yml Updated actions/checkout from v2 to v3; setup-java from v2 to v4; distribution from 'adopt' to 'temurin'.
.github/workflows/sast.yml Updated setup-java from v2 to v4; changed Java distribution from 'adopt' to 'temurin'.

Suggested reviewers

  • drtechie

Poem

In the warren where the workflows hop,
Java's brew gets a shiny new top.
From 'adopt' to 'temurin', we leap with glee,
Actions v4β€”how modern we’ll be!
With paws on the pipeline, the builds run anew,
Rabbits and reviewers, this update’s for you!
πŸ‡βœ¨


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
πŸͺ§ Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • 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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @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.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
.github/workflows/package.yml (1)

23-23: Remove trailing whitespace
The - name: Checkout code line has trailing spaces; please remove them to satisfy YAML linting rules.

🧰 Tools
πŸͺ› YAMLlint (1.35.1)

[warning] 23-23: wrong indentation: expected 6 but found 4

(indentation)


[error] 23-23: trailing spaces

(trailing-spaces)

.github/workflows/sast.yml (1)

43-44: Fix YAML indentation under with:
The java-version and distribution keys are over-indented by two spaces. They should be aligned directly under with: (two spaces deeper than with:).

-      with:
-          java-version: 17
-          distribution: 'temurin'
+      with:
+        java-version: 17
+        distribution: 'temurin'
🧰 Tools
πŸͺ› YAMLlint (1.35.1)

[warning] 43-43: wrong indentation: expected 8 but found 10

(indentation)

πŸ“œ Review details

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

πŸ“₯ Commits

Reviewing files that changed from the base of the PR and between 1d369e6 and 4dc2061.

πŸ“’ Files selected for processing (3)
  • .github/workflows/build-on-pull-request.yml (2 hunks)
  • .github/workflows/package.yml (1 hunks)
  • .github/workflows/sast.yml (1 hunks)
🧰 Additional context used
πŸͺ› actionlint (1.7.4)
.github/workflows/package.yml

24-24: the runner of "actions/checkout@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

πŸͺ› YAMLlint (1.35.1)
.github/workflows/package.yml

[error] 25-25: trailing spaces

(trailing-spaces)

.github/workflows/sast.yml

[warning] 43-43: wrong indentation: expected 8 but found 10

(indentation)

πŸ”‡ Additional comments (4)
.github/workflows/build-on-pull-request.yml (1)

16-20: Upgrade and standardize Java setup to v4 with Temurin
The Setup JDK 17 step has been updated to use actions/setup-java@v4 and the temurin distribution, aligning it with other workflows.

.github/workflows/package.yml (2)

23-24: Upgrade checkout action to v3
The actions/checkout step has been upgraded from @v2 to @v3, ensuring compatibility with the latest GitHub Actions runner features.

🧰 Tools
πŸͺ› actionlint (1.7.4)

24-24: the runner of "actions/checkout@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

πŸͺ› YAMLlint (1.35.1)

[warning] 23-23: wrong indentation: expected 6 but found 4

(indentation)


[error] 23-23: trailing spaces

(trailing-spaces)


27-30: Upgrade and standardize Java setup to v4 with Temurin
The Setup JDK 17 step now uses actions/setup-java@v4 with the temurin distribution, matching other CI workflows for consistency.

.github/workflows/sast.yml (1)

40-44: Upgrade and standardize Java setup to v4 with Temurin
Updated the Setup JDK 17 step to actions/setup-java@v4 and switched the distribution to temurin. This aligns with the other workflows and introduces no breaking changes.

🧰 Tools
πŸͺ› YAMLlint (1.35.1)

[warning] 43-43: wrong indentation: expected 8 but found 10

(indentation)

Copy link

sonarqubecloud bot commented May 2, 2025

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (3)
.github/workflows/package.yml (1)

23-24: Use latest checkout action and correct indentation
Updated the checkout step to actions/checkout@v3 to leverage the latest stable release. Also adjust the indentation under steps: so that list items are two spaces in from the steps: key (6 spaces total) to satisfy YAML lint.

Proposed diff:

   steps:
-    - name: Checkout code
-      uses: actions/checkout@v3
+      - name: Checkout code
+        uses: actions/checkout@v3
🧰 Tools
πŸͺ› actionlint (1.7.4)

24-24: the runner of "actions/checkout@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

πŸͺ› YAMLlint (1.35.1)

[warning] 23-23: wrong indentation: expected 6 but found 4

(indentation)

.github/workflows/sast.yml (2)

30-35: Use checkout v3 and fix with block indentation
Bumped actions/checkout to @v3 and added explicit ref and repository inputs. Adjust the indentation of the with: block so its keys are two spaces in from the with: key, satisfying YAML lint.

Proposed diff:

   steps:
-      - name: Checkout code
-        uses: actions/checkout@v3
-        with:
-            ref: ${{ github.event.pull_request.head.ref }}
-            repository: ${{ github.event.pull_request.head.repo.full_name }}
+      - name: Checkout code
+        uses: actions/checkout@v3
+        with:
+          ref: ${{ github.event.pull_request.head.ref }}
+          repository: ${{ github.event.pull_request.head.repo.full_name }}
🧰 Tools
πŸͺ› actionlint (1.7.4)

31-31: the runner of "actions/checkout@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

πŸͺ› YAMLlint (1.35.1)

[warning] 33-33: wrong indentation: expected 10 but found 12

(indentation)


40-45: Upgrade Java setup action & clean up formatting
The actions/setup-java step is now @v4 with distribution: 'temurin', matching the package workflow. Refine the indentation of the with: inputs and remove trailing spaces on the block for consistency.

Proposed diff:

       - name: Setup JDK 17
-      uses: actions/setup-java@v4
+        uses: actions/setup-java@v4
       with:
-            java-version: 17
-            distribution: 'temurin'
+          java-version: 17
+          distribution: 'temurin'
🧰 Tools
πŸͺ› YAMLlint (1.35.1)

[warning] 43-43: wrong indentation: expected 10 but found 12

(indentation)


[error] 45-45: trailing spaces

(trailing-spaces)

πŸ“œ Review details

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

πŸ“₯ Commits

Reviewing files that changed from the base of the PR and between 4dc2061 and 1353aaf.

πŸ“’ Files selected for processing (2)
  • .github/workflows/package.yml (1 hunks)
  • .github/workflows/sast.yml (1 hunks)
🧰 Additional context used
πŸͺ› actionlint (1.7.4)
.github/workflows/package.yml

24-24: the runner of "actions/checkout@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

.github/workflows/sast.yml

31-31: the runner of "actions/checkout@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)


38-38: the runner of "github/codeql-action/init@v2" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)


50-50: the runner of "github/codeql-action/analyze@v2" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

πŸͺ› YAMLlint (1.35.1)
.github/workflows/package.yml

[warning] 23-23: wrong indentation: expected 6 but found 4

(indentation)


[error] 25-25: trailing spaces

(trailing-spaces)

.github/workflows/sast.yml

[warning] 33-33: wrong indentation: expected 10 but found 12

(indentation)


[warning] 43-43: wrong indentation: expected 10 but found 12

(indentation)


[error] 45-45: trailing spaces

(trailing-spaces)

πŸ”‡ Additional comments (1)
.github/workflows/package.yml (1)

27-30: Upgrade Java setup to v4 and switch distribution
The actions/setup-java step has been bumped from @v2 to @v4 and the distribution changed from adopt to temurin, aligning with other workflows. This matches recommended defaults for modern Java CI.

@drtechie drtechie merged commit d74cc05 into PSMRI:develop May 3, 2025
2 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.

2 participants