gradle-git-publish

This release upgrades to grgit 3. Other than grgit's breaking changes, nothing has changed in this plugin.

Breaking Changes

• #58 Upgraded to grgit 3 to fix incompatibility with Groovy 2.5 / Gradle 5.

Enhancements

None

Fixes

None

Deprecations

None

Compatibility

Tested on the following version:

This is a fix release to address an issue where you could see NoSuchRemoteException: origin: not found when gitPublishReset runs.

Breaking Changes

None

Enhancements

None

Fixes

• #51 NoSucheRemoteException when running gitPublishReset

Deprecations

None

Compatibility

Tested on the following version:

This is a fix release to address an issue where you could see NoSuchRemoteException: origin: not found when gitPublishReset runs.

Breaking Changes

None

Enhancements

None

Fixes

• #51 NoSucheRemoteException when running gitPublishReset

Deprecations

None

Compatibility

Tested on the following version:

This is a fix release to (hopefully) address an issue where you could see NoSuchRemoteException: origin: not found when gitPublishReset runs.

Breaking Changes

None

Enhancements

None

Fixes

• #51 NoSucheRemoteException when running gitPublishReset

Deprecations

None

Compatibility

Tested on the following version:

With the changes in 0.4.0 not resulting in any major issues reported, gradle-git-publish can now move to 1.0.0.

This change only includes a minor performance fix since 0.4.1.

For users upgrading from <0.4.0, the use of Property on the extension removes the ability to assign GString transparently. This is due to gradle/gradle#3005.

gitPublish {
  // This will no longer work
  commitMessage = "Deploy docs to gh-pages (${grgit.head().abbreviatedId})"
  // Must change to this
  commitMessage = "Deploy docs to gh-pages (${grgit.head().abbreviatedId})".toString()
}

Breaking Changes

None

Enhancements

None

Fixes

• #46 Internal Grgit provider is now memoized, avoiding reopening or re-cloning the Git repo
• POM on Gradle Plugin Portal now includes static versions instead of ranges

Deprecations

None

Compatibility

Tested on the following version:

With the changes in 0.4.0 not resulting in any major issues reported, gradle-git-publish can now move to 1.0.0.

This change only includes a minor performance fix since 0.4.1.

Breaking Changes

None

Enhancements

None

Fixes

• #46 Internal Grgit provider is now memoized, avoiding reopening or re-cloning the Git repo
• POM on Gradle Plugin Portal now includes static versions instead of ranges

Deprecations

None

Compatibility

Tested on the following version:

With the changes in 0.4.0 not resulting in any major issues reported, gradle-git-publish can now move to 1.0.0.

This change only includes a minor performance fix since 0.4.1.

Breaking Changes

None

Enhancements

None

Fixes

• #46 Internal Grgit provider is now memoized, avoiding reopening or re-cloning the Git repo

Deprecations

None

Compatibility

Tested on the following version:

A small fix release to restore a default to its pre-0.4.0 value.

For users upgrading from <0.4.0, the use of Property on the extension removes the ability to assign GString transparently. This is due to gradle/gradle#3005.

gitPublish {
  // This will no longer work
  commitMessage = "Deploy docs to gh-pages (${grgit.head().abbreviatedId})"
  // Must change to this
  commitMessage = "Deploy docs to gh-pages (${grgit.head().abbreviatedId})".toString()
}

Breaking Changes

None

Enhancements

None

Fixes

• #47 Default commit message didn't match documentation

Deprecations

None

Compatibility

Tested on the following version:

A small fix release to restore a default to its pre-0.4.0 value.

Breaking Changes

None

Enhancements

None

Fixes

• #47 Default commit message didn't match documentation

Deprecations

None

Compatibility

Tested on the following version:

A breaking release to address an issue with task dependencies, particularly implicit dependencies from adding to the gitPublish.contents CopySpec. All tasks were rewritten as concrete task classes, instead of declaring ad-hoc ones. This involved using Gradle's new-ish Provider API, raising the minimum Gradle version to 4.3.

For users upgrading from <0.4.0, the use of Property on the extension removes the ability to assign GString transparently. This is due to gradle/gradle#3005.

gitPublish {
  // This will no longer work
  commitMessage = "Deploy docs to gh-pages (${grgit.head().abbreviatedId})"
  // Must change to this
  commitMessage = "Deploy docs to gh-pages (${grgit.head().abbreviatedId})".toString()
}

Breaking Changes

• Requires Gradle 4.3+ due to use of Provider API for lazy configuration of rewritten task classes

Enhancements

• Update from grgit 2.1.1 to 2.2.0

Fixes

• #41 gitPublishCopy doesn't have implicit dependencies on inputs of gitPublish.contents anymore

Deprecations

None

Compatibility

Tested on the following version:

A breaking release to address an issue with task dependencies, particularly implicit dependencies from adding to the gitPublish.contents CopySpec. All tasks were rewritten as concrete task classes, instead of declaring ad-hoc ones. This involved using Gradle's new-ish Provider API, raising the minimum Gradle version to 4.3.

Changes since rc.1 Converted remaining plugin code to Java and use of Provider API for lazy configuration.

Breaking Changes

• Requires Gradle 4.3+ due to use of Provider API for lazy configuration of rewritten task classes

Enhancements

• Update from grgit 2.1.1 to 2.2.0

Fixes

• #41 gitPublishCopy doesn't have implicit dependencies on inputs of gitPublish.contents anymore

Deprecations

None

Compatibility

Tested on the following version:

A breaking release to address an issue with task dependencies, particularly implicit dependencies from adding to the gitPublish.contents CopySpec. All tasks were rewritten as concrete task classes, instead of declaring ad-hoc ones. This involved using Gradle's new-ish Provider API, raising the minimum Gradle version to 4.3.

Breaking Changes

• Requires Gradle 4.3+ due to use of Provider API for lazy configuration of rewritten task classes

Enhancements

• Update from grgit 2.1.1 to 2.2.0

Fixes

• #41 gitPublishCopy doesn't have implicit dependencies on inputs of gitPublish.contents anymore

Deprecations

None

Compatibility

Tested on the following version:

A breaking release to address an issue with task dependencies, particularly implicit dependencies from adding to the gitPublish.contents CopySpec. All tasks were rewritten as concrete task classes, instead of declaring ad-hoc ones. This involved using Gradle's new-ish Provider API, raising the minimum Gradle version to 4.3.

Breaking Changes

• Requires Gradle 4.3+ due to use of Provider API for lazy configuration of rewritten task classes

Enhancements

None

Fixes

• #41 gitPublishCopy doesn't have implicit dependencies on inputs of gitPublish.contents anymore

Deprecations

None

Compatibility

Tested on the following version:

This release bumps dependencies.

Breaking Changes

None

Enhancements

None

Fixes

None

Deprecations

None

Compatibility

Java: requires 8 or higher
Gradle: tested against 3.0, 3.1, 3.2, 3.2.1. 3.3, 3.4, 3.5, 3.5.1, 4.0, 4.0.1, 4.0.2, 4.1, 4.2, 4.2.1, 4.3, 4.3.1, 4.4, 4.4.1, 4.5, 4.5.1

Known Issues

• #41 gitPublishCopy doesn't have implicit dependencies on inputs of gitPublish.contents anymore

This is a fix release to address some new behavior in Gradle 4.2 that highlighted some misconfigured task outputs.

Breaking Changes

None

Enhancements

None

Fixes

• #35 Failures during gitPublishCopy or gitPublishCommit in Gradle 4.2

Deprecations

None

Compatibility

Java: requires 8 or higher
Gradle: tested against 3.0, 3.1, 3.2, 3.2.1. 3.3, 3.4, 3.5, 3.5.1, 4.0, 4.0.1, 4.0.2, 4.1, 4.2

Known Issues

• #41 gitPublishCopy doesn't have implicit dependencies on inputs of gitPublish.contents anymore

This is a fix release to address some new behavior in Gradle 4.2 that highlighted some misconfigured task outputs.

Breaking Changes

None

Enhancements

None

Fixes

• #35 Failures during gitPublishCopy or gitPublishCommit in Gradle 4.2

Deprecations

None

Compatibility

Java: requires 8 or higher
Gradle: tested against 3.0, 3.1, 3.2, 3.2.1. 3.3, 3.4, 3.5, 3.5.1, 4.0, 4.0.1, 4.0.2, 4.1, 4.2

This is a fix release to address some new behavior in Gradle 4.2 that highlighted some misconfigured task outputs.

Breaking Changes

None

Enhancements

None

Fixes

• #35 Failures during gitPublishCopy or gitPublishCommit in Gradle 4.2

Deprecations

None

Compatibility

Java: requires 8 or higher
Gradle: tested against 3.0, 3.1, 3.2, 3.2.1. 3.3, 3.4, 3.5, 3.5.1, 4.0, 4.0.1, 4.0.2, 4.1, 4.2

This is a fix release

Breaking Changes

None

Enhancements

None

Fixes

• #37 Plugin didn't respect repoDir property on extension
• #32 Deprecation warning for dependsOnTaskDidWork()

Deprecations

None

Compatibility

Java: requires 8 or higher
Gradle: tested against 3.0, 3.1, 3.2, 3.2.1. 3.3, 3.4, 3.5, 3.5.1, 4.0, 4.0.1, 4.0.2, 4.1, 4.2

This release is focused on Grgit 2 compatibility.

Breaking Changes

• Updated dependency on org.ajoberstar:grgit to 2.0.0
• Removed the gitPublishClose task. The repo is now closed via a build listener.

Enhancements

None

Fixes

None

Deprecations

None

Compatibility

Java: requires 8 or higher
Gradle: tested against 3.0, 3.1, 3.2, 3.2.1. 3.3, 3.4, 3.5, 3.5.1, 4.0, 4.0.1, 4.0.2, 4.1, 4.2

This release is focused on Grgit 2 compatibility.

Breaking Changes

• Updated dependency on org.ajoberstar:grgit to 2.0.0-rc.1
• Removed the gitPublishClose task. The repo is now closed via a build listener.

Enhancements

None

Fixes

None

Deprecations

None

Compatibility

Java: requires 8 or higher
Gradle: tested against 3.0, 3.1, 3.2, 3.2.1. 3.3, 3.4, 3.5, 3.5.1, 4.0, 4.0.1, 4.0.2