Regression on the API? `ref_name invalid` on `/api/v4/projects/<project_id>/repository/commits`

ref_name invalid on /api/v4/projects/<project_id>/repository/commits

Hi!
I’ve been using GitLab’s REST API for years, and all of a sudden today I started having 400 errors on the /api/v4/projects/<project_id>/repository/commits endpoint, with the following message:

{
  "error": "ref_name is invalid"
}

The ref_name I provide has the following format: <commit_hash1>..<commit_hash2>.

Like I said above, this script has been working for years without any issue, and it started responding with errors today at around 7AM (UTC). I can’t reproduce the error on the API of my self-hosted instance of GitLab.

Is there any known regression or deprecation of this parameter? I didn’t see anything that seemed closely related to that in the changelog.

Thanks for your help!

1 Like

It turns out this is indeed a regression, and a fix is on its way.