Skip to content

Releases: spring-io/develocity-conventions

v0.0.22

01 Oct 11:22
Compare
Choose a tag to compare

⭐ New Features

  • Use spring.build-type to control the Gradle conventions' behavior #96

v0.0.21

11 Sep 09:30
Compare
Choose a tag to compare

⭐ New Features

  • Remove the need for Gradle projects to depend on the com.gradle.develocity plugin #92

📔 Documentation

  • Document how GitHub Actions is detected #95

🔨 Dependency Upgrades

  • Upgrade to Develocity Gradle Plugin 3.18.1 #93

v0.0.20

20 Aug 15:50
Compare
Choose a tag to compare

⭐ New Features

  • Support Develocity Maven Extension 1.22 #90
  • Support Develocity Gradle Plugin 3.18 #89
  • Raise the minimum supported version of Gradle to 7.4 #87

🐞 Bug Fixes

  • Maven Conventions do not correctly handle a failure that occurs when running a process #86

v0.0.19

08 Jul 10:23
Compare
Choose a tag to compare

🐞 Bug Fixes

  • Remote build cache is not enabled when using Maven conventions #83

📔 Documentation

  • Document Docker Compose custom value #84

v0.0.18

02 Jul 11:11
Compare
Choose a tag to compare

⚠️ Noteworthy Changes

  • Following the rebranding of Gradle Enterprise to Develocity, the conventions have been renamed.
    The ID of the Gradle plugin is now io.spring.develocity.conventions.

⭐ New Features

  • Rename to Develocity Conventions #82
  • Reinstate Maven support #81
  • Capture Docker Compose version information in a custom value #80
  • Capture Docker version information in a custom value #79
  • Build scan fails when git isn't available #54

v0.0.17

25 Apr 16:48
Compare
Choose a tag to compare

⚠️ Noteworthy Changes

  • When upgrading to this release you must migrate from the com.gradle.enterprise plugin to the com.gradle.develocity plugin at the same time
  • The build cache now uses the same access token as build scans for authentication. To avoid a deprecation warning, provide this access key using the DEVELOCITY_ACCESS_KEY environment variable rather than the GRADLE_ENTERPRISE_ACCESS_KEY environment variable. GRADLE_ENTERPRISE_CACHE_USERNAME and GRADLE_ENTERPRISE_CACHE_PASSWORD environment variables are no longer needed and should be removed

⭐ New Features

  • Add a custom value for the detected CI provider #77
  • Support the com.gradle.develocity plugin in place of the com.gradle.enterprise plugin #74
  • Authenticate with the build cache using an access token #73

📔 Documentation

  • Update README to reflect conventions being published to Maven Central #76

v0.0.16

28 Mar 11:18
Compare
Choose a tag to compare

⭐ New Features

  • Automatically detect GitHub Actions as a CI environment #72

v0.0.15

16 Jan 11:53
Compare
Choose a tag to compare

⭐ New Features

  • Don't publish build scans when the properties task may run #69

🔨 Dependency Upgrades

  • Upgrade to Gradle Enterprise Gradle Plugin 3.16 #68

v0.0.14

10 Aug 14:20
Compare
Choose a tag to compare

🔨 Dependency Upgrades

  • Upgrade to Gradle Enterprise Gradle Plugin 3.14 #63

v0.0.13

06 Jan 14:48
Compare
Choose a tag to compare

⭐ New Features

  • Sign published artifacts #59
  • Publish the conventions to Maven Central #58