changelog-app[bot]
commented
3 weeks 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
rhuffy
General
As a FLUP to this comment: https://github.com/palantir/atlasdb/pull/7141#discussion_r1631013728, we can now write custom ErrorProne rules on this repo. The first one i've added just asserts that any non-abstract classes with a name starting with "Default" must be final.
After this PR:
==COMMIT_MSG== Custom ErrorProne rules - DefaultClassMustBeFinal ==COMMIT_MSG==
Please tag any other people who should be aware of this PR: @jeremyk-91 @jkozlowski