CHW-4900 RubyGemsDependencyAPIDeprecated
rubygems /api/v1/dependencies was deprecated upstream in 2023; use the Compact Index (versions, names, info/{name}), /api/v1/versions/{name}.json, or the legacy Marshal indexes (specs.4.8.gz) instead
Default message: rubygems /api/v1/dependencies was deprecated upstream in 2023; use the Compact Index (versions, names, info/{name}), /api/v1/versions/{name}.json, or the legacy Marshal indexes (specs.4.8.gz) instead
HTTP status:410(client)
Reason:UPSTREAM_DEPRECATED
Problem. A request to /api/v1/dependencies through the RubyGems
proxy returns HTTP 410 Gone. Cause. RubyGems.org deprecated the
Dependency API in February 2023. Upstream answers with a 404 and a
text/plain body; the proxy rewrites that into a 410 with a structured
CHW envelope so the failure is machine-readable and points at the
working successors. Fix. Move the client onto one of the supported
index endpoints:
- the Compact Index —
versions,names,info/{name}(what Bundler ≥ 1.12 uses by default), /api/v1/versions/{name}.jsonfor a single gem’s version list, or- the legacy Marshal indexes —
specs.4.8.gz,latest_specs.4.8.gz,prerelease_specs.4.8.gz.
In practice only a very old Bundler or a bespoke script still calls the Dependency API; upgrading Bundler resolves it. HTTP 410.