Hiding refused versions is for internal organisations only
type | https://docs.frem.sh/reference/api/errors/metadata-filter-internal-only |
| HTTP status | 403 Forbidden |
What it means
The request set metadata_filter to on on PUT /orgs/{org}/dependency-proxy, and the organisation is not one of fremforge’s internal organisations. With on, the dependency proxy leaves the versions your package policy would refuse out of the package metadata it serves. That value is not available to customer organisations yet, whoever asks, and nothing in the request was saved.
Example detail messages returned with this error:
- metadata_filter “on” is available on internal organisations only until package policy enforcement is decided; “shadow” logs what it would hide.
What to do
Send metadata_filter as off or shadow instead, or leave it out. The other dependency proxy settings can be saved as usual.
Response shape
All fremforge API errors are RFC 9457 problem+json:
{
"type": "https://docs.frem.sh/reference/api/errors/metadata-filter-internal-only",
"title": "Forbidden",
"status": 403,
"detail": "..."
}Branch on type, not on title or detail - those are human-readable and may be reworded.