AdamOswald / hexios

0 stars 0 forks source link

Update gradle/actions action to v4 #23

Closed renovate[bot] closed 2 months ago

renovate[bot] commented 3 months ago

Mend Renovate

This PR contains the following updates:

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

[!WARNING] Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

gradle/actions (gradle/actions) ### [`v4.0.0`](https://togithub.com/gradle/actions/releases/tag/v4.0.0) [Compare Source](https://togithub.com/gradle/actions/compare/v3.5.0...v4.0.0) 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](https://togithub.com/gradle/actions/blob/v4.0.0-rc.1/docs/deprecation-upgrade-guide.md#using-the-action-to-execute-gradle-via-the-arguments-parameter-is-deprecated). ##### Cache cleanup enabled by default After a number of fixes and improvements, this release enables [cache-cleanup](https://togithub.com/gradle/actions/blob/v4.0.0-rc.1/docs/setup-gradle.md#configuring-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](https://togithub.com/gradle/actions/issues/71)) - Cache cleanup is not run after configuration-cache reuse ([#​19](https://togithub.com/gradle/actions/issues/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](https://togithub.com/gradle/actions/issues/12)): - The `allow-snapshot-wrappers` makes it possible to validate snapshot wrapper jars using `setup-gradle`. - Checksums for [nightly and snapshot Gradle versions](https://services.gradle.org/distributions-snapshots/) are now validated ([#​281](https://togithub.com/gradle/actions/issues/281)). - Valid wrapper checksums are cached in Gradle User Home, reducing the need to retrieve checksum values remotely ([#​172](https://togithub.com/gradle/actions/issues/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](https://togithub.com/gradle/actions/issues/171)) - Improved error message when `wrapper-validation` finds no wrapper jars ([#​284](https://togithub.com/gradle/actions/issues/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 generated - `dependency-graph-exclude-projects` and `dependency-graph-include-projects`: [select which Gradle projects will contribute to the generated dependency graph](https://togithub.com/gradle/actions/blob/v4.0.0-rc.1/docs/dependency-submission.md#selecting-gradle-projects-that-will-contribute-to-the-dependency-graph). - `dependency-graph-exclude-configurations` and `dependency-graph-include-configurations`: [select which Gradle configurations will contribute to the generated dependency graph](https://togithub.com/gradle/actions/blob/v4.0.0-rc.1/docs/dependency-submission.md#selecting-gradle-configurations-that-will-contribute-to-the-dependency-graph). ##### Other improvements - In Job summary, the action now provides an explanation when cache is set to `read-only` or `disabled` ([#​255](https://togithub.com/gradle/actions/issues/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](https://togithub.com/gradle/actions/issues/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](https://togithub.com/gradle/actions/issues/290)) #### Deprecations and breaking changes - The `gradle-home-cache-cleanup` input parameter has been deprecated and replaced by `cache-cleanup` - The undocumented `dependency-graph: clear` parameter has been removed without replacement - The following parameters deprecated in `v3` have been removed: - [arguments](https://togithub.com/gradle/actions/blob/v4.0.0-rc.1/docs/deprecation-upgrade-guide.md#using-the-action-to-execute-gradle-via-the-arguments-parameter-is-deprecated) - [build-scan-terms-of-service-url and build-scan-terms-of-service-agree](https://togithub.com/gradle/actions/blob/v4.0.0-rc.1/docs/deprecation-upgrade-guide.md#the-build-scan-terms-of-service-input-parameters-have-been-renamed) #### Changelog - Only fetch checksums for unknown wrapper versions by [@​bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/actions/pull/292](https://togithub.com/gradle/actions/pull/292) - Isolate 'dependency-submission' action from 'setup-gradle' by [@​bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/actions/pull/293](https://togithub.com/gradle/actions/pull/293) - Caching improvements by [@​bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/actions/pull/294](https://togithub.com/gradle/actions/pull/294) - Config cache cleanup by [@​bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/actions/pull/295](https://togithub.com/gradle/actions/pull/295) - Delete excluded paths on restore Gradle Home by [@​bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/actions/pull/298](https://togithub.com/gradle/actions/pull/298) - Use faster D: drive on windows for Gradle User Home and Gradle downloads by [@​bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/actions/pull/299](https://togithub.com/gradle/actions/pull/299) - Always set the GRADLE_USER_HOME env var by [@​bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/actions/pull/300](https://togithub.com/gradle/actions/pull/300) - Fix windows by [@​bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/actions/pull/302](https://togithub.com/gradle/actions/pull/302) - Use pre-installed Gradle when available by [@​bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/actions/pull/301](https://togithub.com/gradle/actions/pull/301) - Prepare for v4 release by [@​bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/actions/pull/303](https://togithub.com/gradle/actions/pull/303) - Include RUNNER_ARCH in cache key by [@​bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/actions/pull/305](https://togithub.com/gradle/actions/pull/305) - Introduce dependency graph params by [@​bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/actions/pull/304](https://togithub.com/gradle/actions/pull/304) - Finish enabling cache-cleanup by default by [@​bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/actions/pull/306](https://togithub.com/gradle/actions/pull/306) - Bump references to Develocity Gradle plugin from 3.17.5 to 3.17.6 by [@​bot-githubaction](https://togithub.com/bot-githubaction) in [https://github.com/gradle/actions/pull/315](https://togithub.com/gradle/actions/pull/315) - Group cache-cleanup log messages by [@​bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/actions/pull/319](https://togithub.com/gradle/actions/pull/319) - Enable wrapper-validation by default in setup-gradle by [@​bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/actions/pull/318](https://togithub.com/gradle/actions/pull/318) - Improve error messages for min-wrapper-count by [@​bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/actions/pull/321](https://togithub.com/gradle/actions/pull/321) **Full Changelog**: https://github.com/gradle/actions/compare/v3.5.0...v4.0.0

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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 these updates again.



This PR was generated by Mend Renovate. View the repository job log.

performance-testing-bot[bot] commented 3 months ago

Unable to locate .performanceTestingBot config file

difflens[bot] commented 3 months ago

View changes in DiffLens

senior-dev-bot[bot] commented 3 months ago

Hi there! :wave: Thanks for opening a PR. :tada: To get the most out of Senior Dev, please sign up in our Web App, connect your GitHub account, and add/join your organization AdamOswald. After that, you will receive code reviews beginning on your next opened PR. :rocket:

coderabbitai[bot] commented 3 months ago

Walkthrough

This update involves upgrading the versions of Gradle actions in several GitHub Actions workflow files. The changes enhance the build process, dependency submission, and overall functionality by incorporating improvements and fixes in the latest action versions. However, these adjustments do not alter the fundamental logic or control flow of the workflows.

Changes

File Path Change Summary
.github/workflows/buildwithgradle.yml Upgraded gradle/actions from v3.3.2 to v4.0.0 and setup-gradle from v3 to v4.
.github/workflows/dependency-submission.yml Updated gradle/actions/dependency-submission from v3 to v4.
.github/workflows/gradle.yml Updated setup-gradle and dependency-submission from v3.3.2 to v4.0.0.

Poem

In a world of code, we hop and play,
Upgrading actions brightens the day!
With Gradle's new shine, our builds will soar,
Bugs be gone, improvements galore!
A rabbit's cheer for changes so fine,
Hopping ahead, our pipeline will shine! 🐰✨


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](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)
Tips ### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `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 as 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. Additionally, you can add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. ### 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](https://docs.coderabbit.ai/guides/configure-coderabbit) 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](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.
guide-bot[bot] commented 3 months ago

Thanks for opening this Pull Request! We need you to:

  1. Fill out the description.

    Action: Edit description and replace <!- ... --> with actual values.

  2. Complete the activities.

    Action: Complete If you want to rebase/retry this PR, check this box

    If an activity is not applicable, use '\~activity description\~' to mark it not applicable.

lang-ci[bot] commented 3 months ago

Issues Summary

1. Permission Denied Error

Logs Summary: Permission denied error occurred while running ./gradlew build. Process completed with exit code 126.

Failing Step:

./gradlew build

Related Source Files: /home/runner/work/hexios/hexios

Related Failures: Java CI with Gradle / build


2. File Not Found Error

Logs Summary: No file in /home/runner/work/hexios/hexios matched to [**/pom.xml], make sure you have checked out the target repository

Failing Step:

Installed distributions

Related Source Files: /home/runner/work/hexios/hexios

Related Failures: Java CI with Maven / build


3. Dependency Resolution Error

Logs Summary: Failed to resolve dependencies for org.ajoberstar.grgit:grgit-core:3.1.1

Failing Step:

Dependency resolution failed

Related Source Files: /home/runner/.m2/repository/org/ajoberstar/grgit/grgit-core/3.1.1/grgit-core-3.1.1.pom, https://files.minecraftforge.net/maven/org/ajoberstar/grgit/grgit-core/3.1.1/grgit-core-3.1.1.pom, https://jcenter.bintray.com/org/ajoberstar/grgit/grgit-core/3.1.1/grgit-core-3.1.1.pom, https://repo.maven.apache.org/maven2/org/ajoberstar/grgit/grgit-core/3.1.1/grgit-core-3.1.1.pom, https://plugins.gradle.org/m2/org/ajoberstar/grgit/grgit-core/3.1.1/grgit-core-3.1.1.pom

Related Failures: Java CI with Gradle / dependency-submission


4. Linting Errors in Checkov, GitHub Actions, JSCPD, YAML, and Super-linter

Logs Summary: Multiple linting errors found in various linters - Checkov, GitHub Actions, JSCPD, YAML, and Super-linter.

Failing Step:

Linting process

Related Source Files: /github/workspace/.github/workflows/gradle.yml

Related Failures: Lint Code Base / run-lint


ℹ️ Help (You can turn this bot off by adding a comment /ai off, or force a refresh of this report with /ai ...) For more support, join our Discord channel
difflens[bot] commented 3 months ago

View changes in DiffLens

secure-code-warrior-for-github[bot] commented 3 months ago

Micro-Learning Topic: Race condition (Detected by phrase)

Matched on "race condition"

What is this? (2min video)

A race condition is a flaw that produces an unexpected result when the timing of actions impact other actions.

Try a challenge in Secure Code Warrior

difflens[bot] commented 3 months ago

View changes in DiffLens

difflens[bot] commented 3 months ago

View changes in DiffLens

difflens[bot] commented 3 months ago

View changes in DiffLens

difflens[bot] commented 2 months ago

View changes in DiffLens

difflens[bot] commented 2 months ago

View changes in DiffLens