Release - 0.6.4

• Removed obsolete console log
• Fix hanging after upgrading

Release - 0.6.3

• Use current working dir (cwd) rather than __dirname to determine build files (__dirname actually returns the directory where the CLI is installed)

Release - 0.6.2

• CLI no longer hangs when a new gradle daemon is started when checking for upgrades
• Use __dirname to determine current working dir rather than "."
• A few more debug logs
• Properly exit process by using process.exit() rather than just returning out of the main function

Release - 0.6.1

• Build file search is now recursively. Previously, only build files below the current directory were found.
• Run will not throw un expected exception, when the versions plugin report is empty

Release - 0.6.0

• More debug logs with live updates (for gradle wrapper upgrades and using the versions plugin)
• Better multi-project support by first reading all files and determining version replacements and then replacing it in every file
• Dependency Upgrades

0.5.3

Minor dependency upgrades and new versions of the gradle versions plugin.

0.5.2 - Fix gradle command detection

Fixed a missing import.

0.5.1 - More debug logs / Relative file path

• To determine the gradle wrapper, a relative path is used
• More debug logs when determining gradle wrapper

0.5.0 - Multi-project builds supported!

Besides the regular dependency updates and internal refactorings, this release adds support for multi-project builds.

Simply run gradle-upgrade-interactive in the root directory.

Issues fixed/implemented in this release:

• #4 in multi-project case the version in the sub-project's build.gradle files do not replaced

Thanks to @lfarkas for reporting an issue.

Release 0.4.1

• Improved the handling of external build files so
  • Multiple files can be inspected
  • Build.gradle(.kts) will still be inspected, when an external file is given
  • Documented the parameter in the README