ip_restriction_ranges in gitlab_group always shows a diff

In my company's environment we manage our top-level group on GitLab SaaS using terraform and we are setting ip_restriction_ranges on that gitlab_group resource to control where people can access it from.

When running a plan to change unrelated settings, or even with no changes made to the resource since the last apply, I'm seeing a diff in the ip_restriction_ranges which is an equivalent set of IP addresses, just ordered differently.

I tried working around it by explicitly sorting the list before passing it to the resource but that doesn't solve the issue.

I'm using provider version 18.6.1.