Releases: palantir/gradle-revapi
Releases · palantir/gradle-revapi
1.1.0
Type |
Description |
Link |
Improvement |
The Revapi analysis task is now cacheable by gradle, reducing the number of time it will need to be run. |
#118 |
1.0.8
Type |
Description |
Link |
Fix |
gradle-revapi will look back at all accepted breaks in the .palantir/revapi.yml , in order to not require PRs being up to date with develop before merging (see #77) |
#97 |
Fix |
gradle-revapi will look back up to 3 git tags if it cannot find the jars for the most recently published git tag. This should fix issues with merging in develop before a develop publish build has succeeded. |
#99 |
1.0.7
Type |
Description |
Link |
Fix |
gradle-revapi will now not fail with errors when adding conjure endpoints or making any other conjure changes (except those that are java breaks but did not trigger conjure-backcompat warning, such as renaming a service or endpoint). |
#85 |
1.0.6
Type |
Description |
Link |
Fix |
Fixes ConcurrentModificationException thrown when com.palantir.baseline (or more specifically com.palantir.baseline-circleci ) is applied before gradle-revapi . |
#79 |
1.0.5
Type |
Description |
Link |
Fix |
gradle-revapi will not spuriously identify the addition of abstract methods from groovy.lang.GroovyObject as breaks. |
#66 |
1.0.4
Type |
Description |
Link |
Fix |
Scala classes are ignored by default by gradle-revapi . |
#42 |
1.0.3
Type |
Description |
Link |
Fix |
revapiAcceptAllBreaks will work on classes that have a string representation including , or starting with @interface . |
#50 |
1.0.2
Type |
Description |
Link |
Fix |
revapiAcceptAllBreaks now works when there are multiple breaks |
#48 |
1.0.1
Type |
Description |
Link |
Fix |
revapiAcceptAllBreaks succeeds when there are no breaking changes |
#46 |
1.0.0
No documented user facing changes