Security lane: unsupported ecosystems

What it means

Returned by PUT /orgs/{org}/dependency-updates/security-fixes/lane with "lane_owner": "security_lane" when the organisation has open fixable findings in ecosystems the Security fixes lane does not fix, for example CRAN or Conan. Hosted Renovate’s own security pull requests cover those today, so switching would quietly lose them. The response’s unsupported_ecosystems lists them, as an object from ecosystem to the number of open fixable findings. Nothing was changed. GET /orgs/{org}/dependency-updates/security-fixes/lane returns the same unsupported_ecosystems, with unsupported_total, before you try. See Taking over from Renovate and Supported ecosystems.

What to do

Fix or dismiss those findings first, or keep Renovate’s security pull requests for this organisation. To switch anyway and accept that those findings get no automatic pull request, send "acknowledge": ["unsupported_ecosystems"] with the request.

Response shape

All fremforge API errors are RFC 9457 problem+json:

{
  "type": "https://docs.frem.sh/reference/api/errors/security-lane-unsupported-ecosystems",
  "title": "Conflict",
  "status": 409,
  "detail": "...",
  "unsupported_ecosystems": { "CRAN": 4, "Conan": 1 }
}

Branch on type, not on title or detail - those are human-readable and may be reworded.