Dependency policies#58
Merged
Merged
Conversation
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.
The standalone policy.md documented a single registry resource as its own file, unlike names/versions/package, whose semantics live as sections in registry-v2.md (e.g. Retiring Releases). Move the policy spec into a Dependency policies section there and drop policy.md.
ericmj
force-pushed
the
dependency-policies
branch
from
3c0746b to
8e9cbe6
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.