changelog-app[bot]
commented
2 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
felixdesouza
CRogers
svc-autorelease
Before this PR
In #2820, we changed the behaviour of baseline-java-versions, but only when Gradle >=8.6 was being used. Now we have upgraded a big chunk of repos to Gradle 8.7 and no issues have appeared.
After this PR
==COMMIT_MSG== Remove pre-Gradle 8.6 baseline-java-versions behaviour. ==COMMIT_MSG==
I'll probably wait a few more days just to check no one reports issues before merging. Wanted to make the PR ahead of time so we don't forget to delete the old behaviour.
Possible downsides?