Add the upkeep standard and track catalog v6.3.0 (v2.1.0)
Added
-
upkeep, a Conditional advisory standard for exhibits that render dated claims about GitLab. A conforming project declares how its claims go stale in.gitlab/freshness.yaml, includes thepipeline/freshnesstripwire on a weekly schedule, publishes afreshness.jsonheartbeatwhen: always, and links a re-derivation procedure from a READMEMaintenancesection. The check asserts the manifest keys, the include, the heading and the link;unasserted:names what the closed primitive set cannot reach. -
The catalog pin moves from
v5.0.0tov6.3.0, the release that shipspipeline/freshness.just syncpropagates it to every include in the repository. Nothing in thev5.0.0tov6.2.2range changes an input contract on a component the reference includes. -
The tripwire cannot withhold a deploy, which is a different property from never going red. Exit 1 (a newer release at the declared cadence, a read date past
stale_after_days, or a citation that returns 404 or 410 or redirects off its host) is red by design, and exit 2 (the check could not see) is the allowed one. Placement keeps it off the critical path: a stage after the deploy, and rules that fire only on scheduled and manually started pipelines.