Rules

FP813 · impact-undeclared

No release impact is declared; flowpact reports the impact the changes require.

Code	Name	Category	Default severity
`FP813`	`impact-undeclared`	Contracts	🔵 info

Why it matters

Without a declaration there is nothing to check against. The required impact is still useful when cutting a release.

Declare the impact: a Conventional Commits pull request title (feat: …, fix!: …), a semver:* label, or --expect.

Change the severity (or turn the rule off) in .github/flowpact/flowpact.config.yml, by code or by name:

.github/flowpact/flowpact.config.yml

rules:
  FP813: off
  # or: impact-undeclared: error

Explain it in the terminal:

flowpact explain FP813

FP812 · impact-over-declared

The pull request declares a bigger impact than its workflow and action changes require.

FP814 · impact-uncertain

A change to a published unit depends on something flowpact cannot evaluate statically.