Alexander Bayandin 07c2411f6b tests: remove mentions of ALLOW_*_COMPATIBILITY_BREAKAGE (#11618) ...

## Problem

There are mentions of `ALLOW_BACKWARD_COMPATIBILITY_BREAKAGE` and
`ALLOW_FORWARD_COMPATIBILITY_BREAKAGE`, but in reality, this mechanism
doesn't work, so let's remove it to avoid confusion.

The idea behind it was to allow some breaking changes by adding a
special label to a PR that would `xfail` the test. However, in practice,
this means we would need to carry this label through all subsequent PRs
until the release (and artifact regeneration). This approach isn't
really viable, as it increases the risk of missing a compatibility break
in another PR.

## Summary of changes
- Remove mentions and handling of
`ALLOW_BACKWARD_COMPATIBILITY_BREAKAGE` /
`ALLOW_FORWARD_COMPATIBILITY_BREAKAGE`

2025-04-17 10:03:21 +00:00

..

actions

tests: remove mentions of ALLOW_*_COMPATIBILITY_BREAKAGE (#11618)

2025-04-17 10:03:21 +00:00

ISSUE_TEMPLATE

[infra/notes] impr: add issue types to issue templates (#10018)

2025-01-31 06:29:06 +00:00

scripts

impr(ci): send clearer notifications to slack when retrying container image pushes (#11447)

2025-04-04 14:56:41 +00:00

workflows

CI(pg-clients): fix workflow permissions (#11623)

2025-04-17 08:54:23 +00:00

actionlint.yml

introduce new runners: unit-perf and use them for benchmark jobs (#11409)

2025-04-15 08:21:44 +00:00

file-filters.yaml

Move cargo-deny into a separate workflow on a schedule (#10289)

2025-01-31 13:42:59 +00:00

pull_request_template.md

Remove checklist from the PR template (#9702)

2024-11-11 17:01:02 +00:00