Previously while testing checkOverbroadConstraints was not ran as part of check so was not in use
After this PR
Now we require checkOverbroadConstraints as part of check so it will be ran on every PR
==COMMIT_MSG==
Add checkOverbroadConstraints to check task
==COMMIT_MSG==
Possible downsides?
If this is merged before an excavator capable of running fix is released it will break upgrades to new versions of gradle-consistent-versions
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.
Before this PR
Previously while testing
checkOverbroadConstraints
was not ran as part ofcheck
so was not in useAfter this PR
Now we require
checkOverbroadConstraints
as part ofcheck
so it will be ran on every PR ==COMMIT_MSG== AddcheckOverbroadConstraints
tocheck
task ==COMMIT_MSG==Possible downsides?
If this is merged before an excavator capable of running fix is released it will break upgrades to new versions of
gradle-consistent-versions