Say the pipeline component index is not a requirement list

Andrew Dunnrequested to merge
standards/pipeline-index-not-required into main

Standard

pipeline

Change type

  • Add new standard
  • Modify existing standard (prose only)
  • Modify existing standard's check.sh (add, remove, or change an assertion)
  • Modify existing standard's templates
  • Status transition: introduced -> enforcing
  • Status transition: enforcing -> archived
  • Retire / archive

What does this MR do and why?

I want the component index to say it lists what exists, because its "Use when" column reads like a rule. Periscope adopted v2.5.0, publishes an image without registry-cleanup, which the index offers to "Projects publishing images", and passes this standard (.gitlab-ci.yml at 31a5261). One preamble line now says a standard's Verify section, not the table, says what is required.

Failure mode this addresses

A reader takes "Every container-shipping project" or "Projects publishing images" as a requirement the check never asserts.

Assertion deltas

None.

Consumer impact

None. The change is prose.

Status transition

None.

Test plan

  • just guard passes (assertions use only closed primitives)
  • just check-one STANDARD=pipeline passes against this repo
  • Ran check.sh against at least one consumer repo of each applicable shape (binary-shipping, lab); results match expectations
  • CHANGELOG updated

check.sh is unchanged. Against periscope at 31a5261 it passes 6 of 6. just ship reports TOTAL: 21 standard(s) passed, 0 exempt, 0 failed.

An AI tool wrote this change and ran the checks above.

Merge request reports