Skip to content

Dependency policies#58

Draft
ericmj wants to merge 7 commits into
mainfrom
dependency-policies
Draft

Dependency policies#58
ericmj wants to merge 7 commits into
mainfrom
dependency-policies

Conversation

@ericmj
Copy link
Copy Markdown
Member

@ericmj ericmj commented May 22, 2026

No description provided.

ericmj added 7 commits May 21, 2026 01:10
Defines /repos/<repository>/policies/<name> as a new signed registry
resource with a Policy protobuf message carrying advisory, retirement,
and cooldown rules. Includes a Visibility enum so the edge can decide
auth gating per-object by decoding the payload.
Unify placeholder casing (REPO/NAME), align advisory wording across
proto and doc, document advisory_min_severity=0 semantics, replace
"AND semantics" with "(intersection)", lift "recommended" to a
normative SHOULD, drop vendor names from proto comments, mark the
gist link as a draft proposal, and tighten name grammar to disallow
leading/trailing non-alphanumerics.
Lowercase MUST/SHOULD to match house prose style, note the
deliberate int64-vs-Timestamp divergence between Policy.published_at
and Release.published_at, drop overly-specific Content-Type detail
from the doc, and signpost that cooldown composes by max-across
where advisory/retirement compose by intersection.
No consumer reads the field: the Hex client switched its cache
staleness check to file mtime, and the Fastly edge only reads
visibility. Field 4 is reserved to prevent reuse.
The previous commit reserved field 4 for back-compat. Nothing's been
released, so the reservation is dead weight — renumber instead.
Docs read as if the system always existed — drop 'existing',
'already', and the 'no new key infrastructure' aside.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant