Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update gradle/actions action to v4 #88

Merged
merged 1 commit into from
Sep 3, 2024

Conversation

renovate-self-hosted-apter[bot]
Copy link
Contributor

@renovate-self-hosted-apter renovate-self-hosted-apter bot commented Sep 1, 2024

This PR contains the following updates:

Package Type Update Change
gradle/actions action major v3.5.0 -> v4.0.1

Release Notes

gradle/actions (gradle/actions)

v4.0.1

Compare Source

This patch release updates a number of dependencies, and fixes a bug that caused Gradle version '8.1' to be confused with '8.10'.

What's Changed

Full Changelog: gradle/actions@v4.0.0...v4.0.1

v4.0.0

Compare Source

Final release of v4.0.0 of the setup-gradle, dependency-submission and wrapper-validation actions provided under gradle/actions.
This release is available under the v4 tag.

Major changes from the v3 release

The arguments parameter has been removed

Using the action to execute Gradle via the arguments parameter was deprecated in v3 and this parameter has been removed.
See here for more details.

Cache cleanup enabled by default

After a number of fixes and improvements, this release enables cache-cleanup by default for all Jobs using the setup-gradle and dependency-submission actions.

Improvements and bugfixes related cache cleanup:

  • By default, cache cleanup is not run if any Gradle build fails (#​71)
  • Cache cleanup is not run after configuration-cache reuse (#​19)

This feature should help to minimize the size of entries written to the GitHub Actions cache, speeding up builds and reducing cache usage.

Wrapper validation enabled by default

In v3, the setup-gradle action was enhanced to support Gradle wrapper validation, removing the need to use a separate workflow
file with the gradle/actions/wrapper-validation action.

With this release, wrapper validation has been significantly improved, and is now enabled by default (#​12):

  • The allow-snapshot-wrappers makes it possible to validate snapshot wrapper jars using setup-gradle.
  • Checksums for nightly and snapshot Gradle versions are now validated (#​281).
  • Valid wrapper checksums are cached in Gradle User Home, reducing the need to retrieve checksum values remotely (#​172).
  • Reduce network calls in wrapper-validation for new Gradle versions: By only fetching wrapper checksums for Gradle versions that were not known when this action was released, this release reduces the likelihood that a network failure could cause failure in wrapper validation (#​171)
  • Improved error message when wrapper-validation finds no wrapper jars (#​284)

Wrapper validation is important for supply-chain integrity. Enabling this feature by default will increase the coverage of wrapper
validation on projects using GitHub Actions.

New input parameters for Dependency Graph generation

Some dependency-graph inputs that could previously only be configured via environment variables now have dedicated action inputs:

Other improvements
  • In Job summary, the action now provides an explanation when cache is set to read-only or disabled (#​255)
  • When setup-gradle requests a specific Gradle version, the action will no longer download and install that version if it is already available on the PATH of the runner (#​270)
  • To attempt to speed up builds, the setup-gradle and dependency-submission actions now attempt to use the D: drive for Gradle User Home if it is available (#​290)

Deprecations and breaking changes

Changelog

Full Changelog: gradle/actions@v3.5.0...v4.0.0


Configuration

📅 Schedule: Branch creation - "before 4am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Copy link
Contributor

coderabbitai bot commented Sep 1, 2024

Walkthrough

The update involves modifying the GitHub Actions workflow configuration by changing the version of the Gradle setup action from v3.5.0 to v4.0.1. This version change may include new features, improvements, or bug fixes, while the overall structure of the workflow remains unchanged.

Changes

Files Change Summary
.github/workflows/build.yml Updated Gradle setup action version from v3.5.0 to v4.0.1.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant GitHub Actions
    participant Gradle

    User->>GitHub Actions: Trigger build
    GitHub Actions->>Gradle: Setup Gradle v4.0.1
    Gradle-->>GitHub Actions: Gradle setup complete
    GitHub Actions->>User: Build process initiated
Loading

Poem

🐇
In the meadow where I play,
A new Gradle version came today.
With hops of joy, we leap and bound,
For smoother builds, we’re glory-bound!
A little change, a brighter day,
Let’s build our dreams, hip-hip-hooray!
🌼


Tip

Early access features: enabled

We are currently testing the following features in early access:

  • Anthropic Claude for code reviews: The new model is designed to enhance code understanding and generation capabilities. We're excited to hear your feedback as we evaluate its performance.

Note:

  • You can enable or disable early access features from the CodeRabbit UI or by updating the CodeRabbit configuration file.
  • Please join our Discord Community to provide feedback and report issues.
  • OSS projects are currently opted into early access features by default.

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
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>.
    • 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 show all the console.log statements in this repository.
    • @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.

Copy link
Contributor

@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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 1428f9a and 41b2035.

Files selected for processing (1)
  • .github/workflows/build.yml (1 hunks)
Additional comments not posted (1)
.github/workflows/build.yml (1)

41-41: Verify the Gradle setup action update from v3.5.0 to v4.0.1.

The new version introduces several updates, including:

  • Dependency updates and a bug fix.
  • Removal of the arguments parameter for executing Gradle.
  • Enabling cache cleanup by default.
  • Improved wrapper validation.
  • New input parameters for generating dependency graphs.
  • Enhanced overall performance and error messaging.

Since this is a major version update, it's important to verify that the workflow runs successfully with the new version to ensure there are no breaking changes.

Please run the workflow with the updated version and confirm that the build process completes successfully. Pay special attention to any steps that were previously relying on the arguments parameter for executing Gradle, as this parameter has been removed in the new version.

Copy link

github-actions bot commented Sep 1, 2024

Branch Coverage (ubuntu-22.04)

Total Project Coverage 69.91%

Copy link

github-actions bot commented Sep 1, 2024

Line Coverage (ubuntu-22.04)

Total Project Coverage 92.05%

Copy link

github-actions bot commented Sep 1, 2024

Branch Coverage (windows-2022)

Total Project Coverage 69.91%

Copy link

github-actions bot commented Sep 1, 2024

Line Coverage (windows-2022)

Total Project Coverage 92.05%

@warnyul warnyul merged commit 9457cd7 into main Sep 3, 2024
9 checks passed
@warnyul warnyul deleted the renovate/gradle-actions-4.x branch September 3, 2024 12:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant