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

Bump gradle/actions from 3.5.0 to 4.0.0 in /.github/workflows #3865

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Aug 12, 2024

Bumps gradle/actions from 3.5.0 to 4.0.0.

Release notes

Sourced from gradle/actions's releases.

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.

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

... (truncated)

Commits
  • af1da67 Prevent concurrent jobs in integ-test-full
  • f8ba43c Better names for suite workflows
  • bcd07e6 Refactor integ-tests into suites
  • d74ee73 Refactor integ-tests
  • fb2e693 [bot] Update dist directory
  • 0719002 Improve error messages for min-wrapper-count (#321)
  • ac3aebd Improve error messages for min-wrapper-count
  • d473db0 Add tests for wrapper-validation with insufficient wrappers
  • 833b05f [bot] Update dist directory
  • 06905c7 Enable wrapper-validation by default in setup-gradle (#318)
  • 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 <dependency name> 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)

violetagg and others added 30 commits December 12, 2023 10:13
this adds extra `if (cancelled)` statement which ensures the `RejectedExecutionException` is not appearing 

---------

Signed-off-by: OlegDokuka <[email protected]>
Signed-off-by: OlegDokuka <[email protected]>
`TimedScheduler` pending tasks count kept increasing when the underlying
`Scheduler` threw `RejectedExecutionException`.

This change catches the exception and immediately stops the
`pendingTasks` sample.

Fixes #3642
After removing the com.gradle.enterprise plugin, we discovered unused
dependency on it in the 3.6.x line. This change removes this dependency
from the multirelease jar setup.
Follow up to #3660 that improves the test stability.
Recent improvements in the automatic context propagation (#3549)
resulted in a regression – some sites where the "last operator" hook was
previously applied no longer saw that behaviour. This change restores
it.

Implementation wise, it's worth noting that the "last operator"
functionality relies on executing the subscribe(Subscriber) method from
the base reactive-streams Publisher instead of the overloads that come
from CorePublisher. The implementations of the reactive-streams base
method in reactor-core apply this hook and that is when something is
considered a "last operator". The wrapping of the Publisher when a
non-internal producer is encountered to restore ThreadLocal values has
changed the compiler's inference of the signature to use the
CoreSubscriber argument variant, breaking the behaviour.

This commit does not bring any tests as the functionality was not
extensively tested before. The issue was discovered in spring-security
in spring-projects/spring-security#14207 and
the change has been validated against the actual use case.
One of the tests for `BoundedElasticThreadPerTaskScheduler` had a race
in it and is now predictably exercised with one more latch.
When `RaceTestUtils`-based concurrency tests involving more tasks than
available CPUs were run, they'd time-out when run in the Java 21 setup
with loom-based boundedElastic `Scheduler`. This change should eliminate
such situations.

Addresses related issues below and potentially more.
Fixes #3629
Fixes #3628
…3685)

Overridden methods from `GenericBoundedElasticThreadPerTaskShedulerTest`
were not previously executed but are now due to [a regression in
junit](junit-team/junit5#3600 (comment)).

This change restores the original behaviour of assumptions and excludes
such tests using the parent class' facility.
This change prevents the same `BoundedElasticThreadPerTaskScheduler` being
picked up when the maximum number of Virtual Threads are already being
executed in parallel. The consequence of improper busyness accounting
was that tasks were executed sequentially instead of being run in
parallel because the same `Worker` was being picked by operators.

Resolves #3857
Recent test failures were observed where `bufferTimeout` case in
`OnDiscardShouldNotLeakTest` failed occasionally due to flaky behaviour
caused by the discard happening shortly after the assertion failed. The
reason was a tiny delay which was not coordinated with the assertion.
This change disables the asynchronous behaviour of the case.
@dependabot dependabot bot requested a review from a team as a code owner August 12, 2024 07:45
@dependabot dependabot bot added the type/dependency-upgrade A dependency upgrade (possibly via bot) label Aug 12, 2024
@violetagg
Copy link
Member

@dependabot recreate

Bumps [gradle/actions](https://github.com/gradle/actions) from 3.5.0 to 4.0.0.
- [Release notes](https://github.com/gradle/actions/releases)
- [Commits](gradle/actions@d9c87d4...af1da67)

---
updated-dependencies:
- dependency-name: gradle/actions
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot changed the base branch from 3.4.x to 3.6.x August 13, 2024 17:10
@dependabot dependabot bot force-pushed the dependabot/github_actions/dot-github/workflows/3.4.x/gradle/actions-4.0.0 branch from 468a0b4 to 4f46a1e Compare August 13, 2024 17:10
@violetagg
Copy link
Member

@dependabot rebase

Copy link
Contributor Author

dependabot bot commented on behalf of github Aug 13, 2024

Looks like this PR is already up-to-date with 3.6.x! If you'd still like to recreate it from scratch, overwriting any edits, you can request @dependabot recreate.

@violetagg
Copy link
Member

This PR needs manual recreation!

@violetagg
Copy link
Member

This is superseded by #3869

@violetagg violetagg closed this Aug 14, 2024
Copy link
Contributor Author

dependabot bot commented on behalf of github Aug 14, 2024

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot dependabot bot deleted the dependabot/github_actions/dot-github/workflows/3.4.x/gradle/actions-4.0.0 branch August 14, 2024 07:07
@violetagg violetagg added status/superseded and removed type/dependency-upgrade A dependency upgrade (possibly via bot) labels Aug 14, 2024
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.