CHW-2301 PolicyReleaseAgeBlocked
Chainsaw error CHW-2301 (HTTP 403): package release is younger than the organization's release-age hold; pin the newest allowed version, wait for this one to age out, or add it to the… Cause and fix.
Default message: package release is younger than the organization’s release-age hold; pin the newest allowed version, wait for this one to age out, or add it to the hold’s exemptions
HTTP status:403(client)
Reason:POLICY_BLOCK
Problem. A download was blocked because the package version was
published more recently than the organization’s release-age hold.
Cause. The hold refuses versions younger than its window — a
guardrail against freshly-published malicious releases, which feeds
typically flag within hours. Version ranges never hit this: the metadata
the proxy serves already omits held versions, so it fires on an exact
pin (usually a lockfile). The response includes package, version,
released_at, release_age_days, min_age_days, hold_hours,
hold_reason (release_hold; release_hold_warn_extended,
release_hold_takeover_extended or release_hold_delta_extended when a
warn verdict, an account-takeover signal or a suspicious change from the
previous version lengthened the hold; release_hold_feed_behind when
offline) and newest_allowed_version.
Fix. Pin newest_allowed_version, wait for the version to age out,
or have an admin add package@version to the hold’s exemptions. Docker
is the exception to “ranges never hit this”: /tags/list is not
filtered and a tag moves to each new build, so a pull by tag is refused
while the tag’s newest build is held; pin an older build by digest
(image@sha256:<digest>), as the refusal message says. HTTP 403.