search

AntoniRokitnicki / AdvancedExpressionFolding

Advanced Java Folding 2 ​(Fork)​
https://plugins.jetbrains.com/plugin/23659-advanced-java-folding-2-fork-
Apache License 2.0
7 stars 2 forks source link

chore(deps): bump gradle/gradle-build-action from 2.4.2 to 2.12.0 #35

Closed dependabot[bot] closed 7 months ago

dependabot[bot] commented 7 months ago

Bumps gradle/gradle-build-action from 2.4.2 to 2.12.0.

Release notes

Sourced from gradle/gradle-build-action's releases.

v2.12.0

Adds a new option to clear a previously submitted dependency-graph.

steps:
- uses: gradle/gradle-build-action@v2
  with:
    dependency-graph: clear

This may prove useful when migrating to a workflow using the upcoming gradle/actions/dependency-submission action.

Full-changelog: https://github.com/gradle/gradle-build-action/compare/v2.11.1...v2.12.0

v2.11.1

This patch release fixes an issue that prevented the gradle-build-action from executing with Gradle 1.12, and improves error reporting for dependency submission failures.

Changelog

  • [FIX] Poor error reporting for dependency-submission failure #1008
  • [FIX] Error with gradle-build-action v2.11.0 and Gradle 1.12: unable to resolve class PluginManager #1007

Full-changelog: https://github.com/gradle/gradle-build-action/compare/v2.11.0...v2.11.1

v2.11.0

In addition to a number of dependency updates, this release:

  • Allows a custom Plugin Repository to be specified when resolving the github-dependency-graph-gradle-plugin. See the documentation for details.
  • Brings increased resilience when failures occur collecting build results or cleaning the Gradle User Home. Such failures should no longer prevent the caching of Gradle User Home or lead to build failures.

Changelog

  • [NEW] Allow a custom plugin repository to be used to resolve dependency-graph plugin #933
  • [FIX] Cache entries and Job Summary not written on cache-cleanup failure #990 #858
  • [FIX] Failure to write build results file should not cause overall build to fail #866

Full-changelog: https://github.com/gradle/gradle-build-action/compare/v2.10.0...v2.11.0

v2.10.0

This release introduces a new artifact-retention-days parameter, which allows a user to configure how long the generated dependency-graph artifacts are retained by GitHub Actions. Adjusting the retention period can be useful to reduce storage costs associated with these dependency-graph artifacts.

See the documentation for more details.

Changelog

Full-changelog: https://github.com/gradle/gradle-build-action/compare/v2.9.0...v2.10.0

v2.9.0

The GitHub dependency-review-action helps you understand dependency changes (and the security impact of these changes) for a pull request. This release updates the GItHub Dependency Graph support to be compatible with the dependency-review-action.

... (truncated)

Commits
  • a8f7551 Build outputs
  • 9283312 Add new option to clear dependency-graph
  • 7c8a278 Remove old clear-dependency-graph action
  • d8ca9b7 Do full checks on release branches
  • 982da8e Attempt to make init-script compatible with Gradle 1.12
  • a0fc860 Build outputs
  • a198078 Improve reporting for dependency-graph failure
  • f95e9c7 Clarify dependency-graph example
  • 8cbcb99 Plugin repository URL is configurable
  • a71aff6 Handle failure in cache-cleanup
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
github-actions[bot] commented 7 months ago

Qodana Community for JVM

57 new problems were found

Inspection name Severity Problems
Loop statement that does not loop 🔶 Warning 10
Constant values 🔶 Warning 9
Result of method call ignored 🔶 Warning 7
Class is exposed outside of its visibility scope 🔶 Warning 4
Octal integer 🔶 Warning 4
Use of Optional.ofNullable with null or not-null argument 🔶 Warning 4
Nullability and data flow problems 🔶 Warning 3
Suspicious usage of compare method 🔶 Warning 2
Confusing 'main()' method 🔶 Warning 2
Inner class may be 'static' 🔶 Warning 2
Optional.get() is called without isPresent() check 🔶 Warning 2
String concatenation as argument to 'StringBuilder.append()' call 🔶 Warning 2
Write-only object 🔶 Warning 2
Mismatched query and update of collection 🔶 Warning 1
Non-serializable class with 'serialVersionUID' 🔶 Warning 1
'Optional' used as field or parameter type 🔶 Warning 1
'Collection.toArray()' call style 🔶 Warning 1

💡 Qodana analysis was run in the pull request mode: only the changed files were checked

View the detailed Qodana report To be able to view the detailed Qodana report, you can either: 1. Register at [Qodana Cloud](https://qodana.cloud/) and [configure the action](https://github.com/jetbrains/qodana-action#qodana-cloud) 2. Use [GitHub Code Scanning with Qodana](https://github.com/jetbrains/qodana-action#github-code-scanning) 3. Host [Qodana report at GitHub Pages](https://github.com/JetBrains/qodana-action/blob/3a8e25f5caad8d8b01c1435f1ef7b19fe8b039a0/README.md#github-pages) 4. Inspect and use `qodana.sarif.json` (see [the Qodana SARIF format](https://www.jetbrains.com/help/qodana/qodana-sarif-output.html#Report+structure) for details) To get `*.log` files or any other Qodana artifacts, run the action with `upload-result` option set to `true`, so that the action will upload the files as the job artifacts: ```yaml - name: 'Qodana Scan' uses: JetBrains/qodana-action@v2023.3.1 with: upload-result: true ```
Contact Qodana team Contact us at [qodana-support@jetbrains.com](mailto:qodana-support@jetbrains.com) - Or via our issue tracker: https://jb.gg/qodana-issue - Or share your feedback: https://jb.gg/qodana-discussions