Releases: palantir/gradle-consistent-versions
Releases · palantir/gradle-consistent-versions
1.25.0
1.24.0
1.23.0
No documented user facing changes
1.22.0
Type | Description | Link |
---|---|---|
Improvement | Expose all lock file constraints as derived from versions.lock in all publications derived from components.java . This will most likely produce surprising behaviour when publishing module metadata! However, we are not using it internally for now, and we are planning a better solution that addresses the problems with the current implementation. |
#504 |
1.21.0
Type | Description | Link |
---|---|---|
Improvement | Expose all lock file constraints as derived from versions.lock in all publications derived from components.java . This will most likely produce surprising behaviour when publishing module metadata! However, we are not using it internally for now, and we are planning a better solution that addresses the problems with the current implementation. |
#504 |
1.20.0
Automated release, no documented user facing changes
1.19.1
1.19.0
Type | Description | Link |
---|---|---|
Improvement | This change relaxes the precondition constraint that checks that configure-on-demand is disabled. We now only require it to be disabled when running the "verifyLocks" task, or when invoked with "--write-locks". This gives projects more flexibility to flag on configure-on-demand in certain scenarios where it might make sense. |
#489 |
1.18.0
Automated release, no documented user facing changes