changelog-app[bot]
commented
4 months ago Generate changelog in changelog-dir>`changelog/@unreleased`</changelog-dir
What do the change types mean?
- `feature`: A new feature of the service. - `improvement`: An incremental improvement in the functionality or operation of the service. - `fix`: Remedies the incorrect behaviour of a component of the service in a backwards-compatible way. - `break`: Has the potential to break consumers of this service's API, inclusive of both Palantir services and external consumers of the service's API (e.g. customer-written software or integrations). - `deprecation`: Advertises the intention to remove service functionality without any change to the operation of the service itself. - `manualTask`: Requires the possibility of manual intervention (running a script, eyeballing configuration, performing database surgery, ...) at the time of upgrade for it to succeed. - `migration`: A fully automatic upgrade migration task with no engineer input required. _Note: only one type should be chosen._How are new versions calculated?
- ❗The `break` and `manual task` changelog types will result in a major release! - 🐛 The `fix` changelog type will result in a minor release in most cases, and a patch release version for patch branches. This behaviour is configurable in autorelease. - ✨ All others will result in a minor version release.Type
Description
svc-autorelease
Before this PR
After this PR
Part of the Gradle JDK automanagement workflow see: https://github.com/palantir/gradle-jdks/issues/333 Required by: https://github.com/palantir/gradle-jdks/pull/341
Adding a
javaVersionspropertysetupJdkToolchains(defaulting to enabled = old workflow). When disabled (via gradle-jdks), theBaselineJavaVersionplugin will set the customjavaCompile/javaLauncher/javaDocToolbased on: https://docs.gradle.org/current/userguide/toolchains.html#toolchains_for_tasks==COMMIT_MSG== Gradle JDK automanagement integration for toolchains ==COMMIT_MSG==
Possible downsides?