E.g. automatically compare v.2.3 with v4.5.6.
Then compare the respective JSON schemas between the tagged versions (like in #438 or v0.4.7...v0.4.8 ). Technical noise could be elimitated by e.g. minifying the JSONs.
Vorschlag 1
Legende: ✔ = kein change, ❌ = change
| compatability of BO Foo |
v0.1.2.3 |
v1.2.4 |
v1.2.5 |
| v.1.2.3 |
✔ |
❌ |
❌ |
| v.1.2.4 |
? |
✔ |
❌ |
| v.1.2.5 |
❌ |
✔ |
✔ |
| compatability of BO Bar |
v0.1.2.3 |
v1.2.4 |
v1.2.5 |
| v.1.2.3 |
✔ |
✔ |
❌ |
| v.1.2.4 |
❌ |
✔ |
❌ |
| v.1.2.5 |
✔ |
✔ |
✔ |
Vorschlag 2
Legende: 🟢 = keine änderung, 🔴 = es hat sich was geändert
| BO |
Versions... |
v1.2.3 |
v1.2.4 |
v1.2.5 |
| MaLo |
|
🟢 |
🟢 |
🔴 |
| Geschäftspartner |
|
🟢 |
🔴 |
🟢 |
Store the matrix statically but also allow to generate it on the fly using an Azure Function or AWS Lambda. You could e.g. use the peter-evans create-pull-request action