- Fix setting version selector for kts build files (#149)
- Fixes for new resolver behaviour that had regressed vs the old resolver
- Fail the build when an incompatible XML parser is on the build classpath with Gradle 8.4+ and 7.6.3 (#139)
- Add kts extension for version selector (new resolver only)
Fixes and enhancements for the internal resolver:
- Handle variants / redirection correctly (#129)
- Handle unresolved libraries due to capability conflicts (#131)
- Per catalog version selectors (#130)
Also fixes an issue where versions weren't correctly grouped to a regression in 0.8.2
🚨 This version introduces a new way to resolve dependencies, no longer depending on the Gradle versions plugin 🚨 This functionality is not enabled by default yet, but can be enabled by setting a property. Please try it out and report any issues you might find!
See the PR on how to enable the new resolver, what the behavioural changes are and some of the rationale behind the change.
- Versions grouping picks the most common version (#127)
- Resolve dependencies from the plugin itself (#123)
- Order of sections in the version catalog is now maintained (#113)
- Added an option to specify the toml file to use for the default tasks (#92)
- Added a warning for plugin dependencies with a version condition that can be upgraded, similar to library dependencies. (#95)
- Removed the compile-time dependency on the versions plugin. This should fix class path issues when the versions plugin is applied from an init script for example. (#97)
- Fixed warnings when configuration cache is enabled (#103)
- Fixed an issue with grouping versions (#82)
- Fix: retain order of kept versions (#78)
- Now also available from the Gradle Plugin portal
- New feature:
--interactive
command line option to stage changes without updating the TOML file (#63) - Shadow (bundle) dependencies to prevent conflicts with other plugins (#39)
- Fix an issue with unused transitive dependencies causing unwanted changes to the TOML file (#71)
- Removed
--add
option. (#69)
- Fix an issue with unused kept pinned dependencies causing the update task to fail (#61)
* Fix an issue with unused kept pinned dependencies causing the update task to fail (#61)
- Fix dropping unused versions when formatting (respecting keep settings) (#54)
- Show message when pinned plugins can be updated (#53)
- Added
versionCatalogFormat
task for formatting only, without updating dependencies. (#48) - The versions plugin is configured to check constraints by default now. At least version
0.4.0
of the versions plugin is required. - Bundles are now formatted with one entry per line and a trailing comma for easier diffing. (#44)
- Retain comments in TOML file (with some limitations) (#18)
- Use
@pin
or@keep
in a comment to pin/keep specific entries - Fixed: Adding dependencies to a version could lead to invalid definitions or update version references in unexpected ways (#36)
- Support plugin declarations without a version (#22)
- Change
sortByKey
to a property so it matches the docs ;)
- Create option now uses the current version used in the project vs the latest version (#13)
- Emit a warning when version declared in the catalog does not match the version used in the project (#8)
- Version conditions (rich versions) in the version block are now handled correctly. If updates are available for a version with a condition, no updates are done automatically, in stead a message will be logged to the console. (#17)
- The
keepUnused
option has been removed from the command line and the plugin configuration and is replaced by the newkeep
option in theversionCatalogUpdate
configuration block. - A new
pin
option has been added to theversionCatalogUpdate
block that allows pinning of entries that should not be automatically updated. This can work in addition with rich version definitions.
- Fixes an issue where plugin dependencies were incorrectly classified as libraries when using a
resolutionStrategy
mapping plugin ids. (#11)
- Use the preferred version for
exceeded
dependencies in the toml file. (#7)
keepUnused = true
keeps unused version declarations too now- Plugins are no longer moved from the libraries section so that a library declaration for a plugin can still be updated.
- Hello, world!