- Allow releasing a final release from older commits within a master branch even when there are newer commits tagged as candidates
- Handle ArtifactoryTask if using build-info-extractor 4.6.0 via @lavcraft (Kirill Tolkachev)
- Cleanup a stray println
- Add in capability for travis to specify a special branch e.g. 2.x or 3.2.x and produce properly versioned snapshots
- Remove optional dependencies so they don't leak onto the classpath when resolved from the plugin portal. It was causing bintray to be upgraded to a version that cannot be compiled against on Gradle 3 and later (only affects the plugin at compile time, not at runtime)
- Builds that fail with Final and candidate builds require all changes to be committed into Git. will now list the files that have not been committed.
- BREAKING: Java 8 is now required
- gradle-git upgraded to 1.7.1
- jgit transitively upgraded to 4.6.1.201703071140-r to address Bug 498759: jgit shows submodule as modified path
- Add some tasks and rework task ordering
- BREAKING:
snapshot
,devSnapshot
,candidate
,final
are no longer finalized by release, they now depend onrelease
- Added
snapshotSetup
,devSnapshotSetup
,candidateSetup
,finalSetup
added if you need to run specific things early in the process - Added
postRelease
task for tasks you want to happen after release (which tags the repo), we have moved publishing to be called by this step
- BREAKING:
- Calculate version in repository with no commits
- Allow pushing tags from detached branch
- Better handle branch patterns that would error out semver when put in dev version
- Fix tasks task so it can run on multiprojects
- Potential BREAKING change: Removing assumptions on whether to enable bintray and artifactory publishes based on whether a user uses the
devSnapshot
,snapshot
,candidate
, orfinal
tasks. These should be on more opinionated plugins.
- Use specific versions of dependencies to prevent dynamic versions in the gradle plugin portal
- upgrade nebula-bintray-plugin 3.2.0 -> 3.3.1
- upgrade gradle-gt plugin 1.3.2 -> 1.4.1
- Remove need for initial tag
- Better error message for release/[invalid semver pattern]
- Better error reporting for missing init tag and uncommitted changes
- Allow to customize the location of Git root
- Update ivy status and project.status on publish
devSnapshot
andsnapshot
will leave status at integrationcandidate
will set ivy and project status to candidatefinal
will set ivy and project status to release
- Also depend on artifactory tasks if creating devSnapshot
- Warn rather than fail when the project contains no git repository or the git repository has no commits.
- Republish correctly
- gradle-git to 1.3.2 // publishing issue
- gradle-git to 1.3.1
- BUGFIX: Allow release from rc tag
- BUGFIX: fix ordering so we don't release if tests are broken
- Move to gradle-git 1.3.0
- Plugin built against gradle 2.6
- New travis release process
- Move to gradle-git 1.2.0
- Only calculate version once for multiprojects
- Move to gradle-git 1.1.0
- Add ability to use major.minor.x branches along with major.x branches.
- Update nebula dependencies to newest releases on 2.2.x branches.
- Modify -Prelease.useLastTag so that it doesn't attempt to push tags to the remote
- Fix to still have
devSnapshot
task work if a user changes the default versioning strategy
- Minor change to allow users to configure the default versioning scheme via gradle-git's release extension
- Add nebula-release properties file so this can be used as a plugin
- rename package from nebula.plugins.release to nebula.plugin.release
- does not include META-INF/gradle-plugins properties file
- Initial release
- Skip straight to 2.2.x to show built and compatible with gradle 2.2