-
Notifications
You must be signed in to change notification settings - Fork 3
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
Conversation
WalkthroughThe update involves modifying the GitHub Actions workflow configuration by changing the version of the Gradle setup action from Changes
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
Poem
Tip Early access features: enabledWe are currently testing the following features in early access:
Note:
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? TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this 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
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 fromv3.5.0
tov4.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.
Branch Coverage (ubuntu-22.04)
|
Line Coverage (ubuntu-22.04)
|
Branch Coverage (windows-2022)
|
Line Coverage (windows-2022)
|
This PR contains the following updates:
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 thesetup-gradle
,dependency-submission
andwrapper-validation
actions provided undergradle/actions
.This release is available under the
v4
tag.Major changes from the
v3
releaseThe
arguments
parameter has been removedUsing the action to execute Gradle via the
arguments
parameter was deprecated inv3
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
anddependency-submission
actions.Improvements and bugfixes related cache cleanup:
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
, thesetup-gradle
action was enhanced to support Gradle wrapper validation, removing the need to use a separate workflowfile with the
gradle/actions/wrapper-validation
action.With this release, wrapper validation has been significantly improved, and is now enabled by default (#12):
allow-snapshot-wrappers
makes it possible to validate snapshot wrapper jars usingsetup-gradle
.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)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:
dependency-graph-report-dir
: sets the location where dependency-graph reports will be generateddependency-graph-exclude-projects
anddependency-graph-include-projects
: select which Gradle projects will contribute to the generated dependency graph.dependency-graph-exclude-configurations
anddependency-graph-include-configurations
: select which Gradle configurations will contribute to the generated dependency graph.Other improvements
read-only
ordisabled
(#255)setup-gradle
requests a specific Gradle version, the action will no longer download and install that version if it is already available on thePATH
of the runner (#270)setup-gradle
anddependency-submission
actions now attempt to use theD:
drive for Gradle User Home if it is available (#290)Deprecations and breaking changes
gradle-home-cache-cleanup
input parameter has been deprecated and replaced bycache-cleanup
dependency-graph: clear
parameter has been removed without replacementv3
have been removed: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.
This PR has been generated by Renovate Bot.