Skip to content

Releases: nebula-plugins/gradle-dependency-lock-plugin

v4.8.0

08 Mar 22:43
Compare
Choose a tag to compare

Performance crucial sections of the plugin are now in Kotlin, improving performance when applying locks

v4.7.0

03 Mar 20:28
Compare
Choose a tag to compare
  • Lock generation will fail when a lock generation task is specified, but dependency locks are ignored using the dependencyLock.ignore property
  • Lock update will fail when a coordinate that is provided by the current project is specified by the dependencyLock.updateDependencies property

v4.6.0

02 Mar 23:25
Compare
Choose a tag to compare
  • Dependency Wayback Machine - new feature that allows projects without dependency locks to have them generated based on a configurable source of dependency data, such as metrics
  • Bug fix - updateLock will now keep first level dependencies from project dependencies locked

v4.5.1

02 Mar 23:20
Compare
Choose a tag to compare

updateLock with updateDependencies now honors overrides.

v4.5.0

27 Feb 20:44
Compare
Choose a tag to compare

Improvements to interactions with plugins such as Nebula dependency recommender, Spring dependency management and resolutionStrategy configurations that affect first order dependencies that do not declare a version.

When a selective updateLock is run (i.e. with -PdependencyLock.updateDependencies specified), locks without a requested version are dropped (as are transitive dependencies currently).

v4.4.0

27 Jan 21:54
Compare
Choose a tag to compare

Compatibility with Gradle 3.4 and it's new unresolvable configurations.

v4.3.2

18 Nov 23:07
Compare
Choose a tag to compare

Only set cache lifetimes on configurations that have not already been resolved, avoiding compatibility issues with Gradle 3.x where configurations are stricter about being modified after being resolved.

v4.3.1

10 Nov 19:07
Compare
Choose a tag to compare
  • Move where we set cache expiry to 0 seconds to taskGraph.whenReady instead of beforeResolve

v4.3.0

03 May 20:27
Compare
Choose a tag to compare

This release significantly improves the reliability and predictability of locking:

  • Locks are now applied by eachDependency.useTarget instead of force. Correctly co-exists with Spring dependency recommender and Spring Boot
  • Locks are applied during incoming.beforeResolve, delaying the application of locks until the last possible moment. Ensures that Android application plugin configurations are locked
  • No longer outputs deprecated lock format warning when an empty dependency lock file exists

v4.2.0

15 Jan 21:54
Compare
Choose a tag to compare
  • Moved to gradle 2.10
  • Fixed updateLock