Rules
FP811 · impact-declaration-conflict
Another source declares a bigger impact than the one the release tool reads.
| Code | Name | Category | Default severity |
|---|---|---|---|
FP811 | impact-declaration-conflict | Contracts | 🔴 error |
Why it matters
Release tools read one thing — usually the squashed commit title. A semver:major label on a fix: pull request looks right in review, but the release is cut as a patch.
How to fix
Make the authoritative source (impact.declaredBy, the title by default) declare the impact, for example feat!: ….
Configure
Change the severity (or turn the rule off) in .github/flowpact/flowpact.config.yml, by code or by name:
rules:
FP811: off
# or: impact-declaration-conflict: errorExplain it in the terminal:
flowpact explain FP811