Update GitHub actions to latest versions

[jodastephen]

• Also reduce maven logging

Summary by CodeRabbit

• Chores
  • Updated versions of GitHub Actions for improved performance and reliability.
  • Enhanced Maven build command for better output and debugging capabilities.

[coderabbitai]

Walkthrough

Walkthrough

The changes involve updates to the versions of several GitHub Actions in the workflow configuration file .github/workflows/build.yml. The actions/checkout and actions/setup-java actions have been upgraded to newer versions, and the github/codeql-action actions have also been updated to a more recent version. Additionally, the Maven build command has been modified to include new flags for improved output during the build process.

Changes

File	Change Summary
.github/workflows/build.yml	Updated versions of actions/checkout, actions/setup-java, and github/codeql-action actions; modified Maven build command to include -B, -e, and -ntp flags.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant GitHub Actions
    participant Maven

    User->>GitHub Actions: Trigger workflow
    GitHub Actions->>GitHub Actions: Checkout code (v4.1.7)
    GitHub Actions->>GitHub Actions: Setup Java (v4.3.0)
    GitHub Actions->>GitHub Actions: Initialise CodeQL (v2.18.4)
    GitHub Actions->>Maven: Run build with flags (-B, -e, -ntp)
    Maven-->>GitHub Actions: Build output
    GitHub Actions-->>User: Workflow complete

Loading

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 2e9d255 and 3c9a2a1.

Files selected for processing (1)

• .github/workflows/build.yml (2 hunks)

Additional comments not posted (4)

.github/workflows/build.yml (4)

29-29: LGTM!

Updating the actions/checkout action to a newer version is a good practice to ensure the latest improvements and bug fixes are included.

---

32-32: LGTM!

Updating the actions/setup-java action to a newer version is a good practice to ensure the latest improvements and bug fixes are included.

---

44-44: LGTM!

Updating the github/codeql-action/init action to a newer version is a good practice to ensure the latest improvements and bug fixes are included.

---

50-50: LGTM!

The changes to the Maven build command and the github/codeql-action/analyze action are beneficial:

• The new flags -B, -e, and -ntp improve the build output and aid in debugging, which is particularly useful in a CI/CD environment.
• Updating the github/codeql-action/analyze action to a newer version ensures the latest improvements and bug fixes are included.

Also applies to: 53-53

---

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:

• 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 generate interesting stats about this repository and render them as a table.
  -- @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 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.