Timofei Larkin 8f2a6bcc87 ci(api-gate): report tightened Application name limits ...

An application declares the limits on its own metadata.name at the
root of its schema, beside properties, where the gate's walk over spec
never looked. A chart lowering its name cap or adding a pattern rejects
names its previous release accepted, which is the same break as
tightening a spec field, so the gate reports it the same way.

Assisted-by: LLM
Signed-off-by: Timofei Larkin <lllamnyp@gmail.com>

2026-09-23 10:59:51 +03:00

..

classify_test.go

ci(api-gate): report tightened Application name limits

2026-09-23 10:59:51 +03:00

classify.go

ci(api-gate): report tightened Application name limits

2026-09-23 10:59:51 +03:00

model.go

fix(ci): catch templated CRDs and APIService-only groups in the API gate

2026-07-06 15:48:07 +03:00

parse_test.go

fix(ci): stop double-parsing every file in the API gate's content walk

2026-07-06 15:48:07 +03:00

parse.go

fix(ci): stop double-parsing every file in the API gate's content walk

2026-07-06 15:48:07 +03:00

report.go

fix(ci): address review of the API gate

2026-07-01 14:51:33 +03:00

schemadiff_test.go

fix(ci): flag constraints added to open maps/arrays

2026-07-01 15:39:24 +03:00

schemadiff.go

ci(api-gate): report tightened Application name limits

2026-09-23 10:59:51 +03:00

snapshot.go

fix(ci): stop double-parsing every file in the API gate's content walk

2026-07-06 15:48:07 +03:00