Skip to content

Releases: palantir/sls-packaging

4.28.0

24 Feb 21:04
24911a5
Compare
Choose a tag to compare
Type Description Link
Improvement JavaServiceDistributionPlugin supports adding java agents using a new javaAgent dependency configuration #1080
Improvement Update YourKit to 2020.9-b424 from 2020.9-b416 #1081

4.27.1

19 Feb 12:53
f0b54a5
Compare
Choose a tag to compare
Type Description Link
Fix If a dependency is discovered (non-optional) but declared explicitly as optional, it will be recognized as optional. #1078

4.27.0

12 Feb 12:44
da821bb
Compare
Choose a tag to compare
Type Description Link
Feature Support optional field in the ProductDependency class.
It also allows discovered dependencies to be set optional through the optionalProductDependency declaration in the manifest.
#1074

4.26.0

17 Dec 20:40
6122e35
Compare
Choose a tag to compare
Type Description Link
Improvement Expose pdeps as a property #1060

4.25.1

17 Dec 18:30
173c6b8
Compare
Choose a tag to compare
Type Description Link
Fix Expose provider on RecommendedProductDependenciesExtension #1059

4.25.0

17 Dec 18:14
51456f4
Compare
Choose a tag to compare
Type Description Link
Improvement Recommended product dependencies doesn't require Java #1058

4.24.1

04 Dec 16:54
d11da85
Compare
Choose a tag to compare
Type Description Link
Fix When parsing the sls-manifest/diagnostics.json file out of jars, sls-packaging no longer performs strict validation on its structure (as this can prevent the rollout of jars which include extra fields). Instead it just passes everything on as long as it's a JSON object. #1054

4.24.0

30 Nov 16:10
c48dbb3
Compare
Choose a tag to compare

Automated release, no documented user facing changes

4.23.1

26 Nov 19:19
ab39a10
Compare
Choose a tag to compare
Type Description Link
Fix The createStartScripts task can now be cached, as it no longer has a lambda attached to it. #1045

4.23.0

25 Nov 16:49
5db6080
Compare
Choose a tag to compare
Type Description Link
Feature For java services, a new diagnostics extension of the sls manifest will be populated based on the sls-manifest/diagnostics.json file found locally or in any jar in runtimeClasspath. Contents should look like {["type": "foo.v1", "docs": "..."]}, as defined in the sls-spec. #1034