Skip to content

Dependency policies#1168

Draft
ericmj wants to merge 1 commit into
mainfrom
dependency-policies
Draft

Dependency policies#1168
ericmj wants to merge 1 commit into
mainfrom
dependency-policies

Conversation

@ericmj
Copy link
Copy Markdown
Member

@ericmj ericmj commented May 22, 2026

No description provided.

Introduce organization-defined dependency policies that filter the
versions available during resolution. A policy is fetched through the
repository like the registry (etag/304, last-known-good fallback,
HEX_OFFLINE) and can constrain dependencies by advisory severity,
retirement reason, and release-age cooldown.

- Hex.Policy and Hex.Policy.{Sources,Filter,Diagnostics}: config
  plumbing via Hex.State, AND-composition of policy sources, atom-space
  advisory/retirement handling, and resolution diagnostics.
- Hex.Registry.Policy / Hex.Registry.Server: policies are prefetched
  and cached alongside the registry.
- Cooldown is policy-aware: setup_cooldown derives the effective cutoff
  from the strictest of the local config and every active policy via
  Hex.Cooldown.strictest/1. The registry/lock-aware bypass builders stay
  in Hex.RemoteConverger (shared with mix hex.outdated).
- mix hex.policy inspects active policies.
- hex_core vendored with Policy resource support.
@ericmj ericmj force-pushed the dependency-policies branch from 6e7e434 to 9c58eb5 Compare June 2, 2026 00:05
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