fineract-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <>
Subject [GitHub] [fineract] renovate-bot opened a new pull request #1001: Update dependency gradle to v6.5
Date Sun, 07 Jun 2020 15:33:19 GMT

renovate-bot opened a new pull request #1001:

   This PR contains the following updates:
   | Package | Update | Change |
   | [gradle]( ([source]( | minor |
`6.4` -> `6.5` |
   ### Release Notes
   ### [`v6.4.1`](
   This is a patch release for Gradle 6.4.
   This fixes several critical bugs in Gradle 6.4:
   -   Regression: Different daemons are used between IDE and CLI builds for the same project
   -   Regression: Main-Class attribute always added to jar manifest when using application
plugin [#&#8203;13057](
   [All issues fixed in this patch release](
   We recommend that you use Gradle 6.4.1 over the initial release of Gradle 6.4.  
   #### Upgrade Instructions
   Switch your build to use Gradle 6.4.1 by updating your wrapper:
   `./gradlew wrapper --gradle-version=6.4.1`
   See the [Gradle 6.x upgrade guide](
to learn about deprecations, breaking changes and other considerations when upgrading to Gradle
   #### Reporting Problems
   If you find a problem with this release, please file a bug on [GitHub Issues](
adhering to our issue guidelines. 
   If you're not sure you're encountering a bug, please use the [forum](
   ### Renovate configuration
   :date: **Schedule**: At any time (no schedule defined).
   :vertical_traffic_light: **Automerge**: Disabled by config. Please merge this manually
once you are satisfied.
   :recycle: **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
   :no_bell: **Ignore**: Close this PR and you won't be reminded about this update again.
    - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box
   This PR has been generated by [WhiteSource Renovate](
View repository job log [here](

This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:

View raw message