Different Version Derived on Gitlab vs Local

Nebula release plugin version 16.1.0.
Gradle version 7.5.1.

Our project is on branch release/2.0.x, branched from tag v2.0.0.

When I run ./gradlew publish final from my local machine I get:

Inferred project: fun-project, version: 2.0.1

This is the correct and expected version.

In Gitlab, I have the following settings:

GIT_FETCH_EXTRA_FLAGS: --tags --prune --prune-tags
GIT_DEPTH: "0"

This, according to the Gitlab documentation, clones the full depth of the repo, and fetches tags.

And the tags are getting pulled because I can see this in the logs:

 * [new branch]      develop               -> origin/develop
 * [new branch]      master                -> origin/master
 * [new branch]      release/2.0.x         -> origin/release/2.0.x
 * [new tag]         v2.0.0                -> v2.0.0
 * [new tag]         v2.0.0-SNAPSHOT       -> v2.0.0-SNAPSHOT

As can be seen, the tag v2.0.0 comes in with the clone. But yet, when the final task runs on Gitlab, it derives the incorrect version:

Inferred project: fun-project, version: 2.1.0

This is the incorrect version per the previous tag and the current branch name.

Start by reproducing the version inference with Gradle 7.5.1 and Nebula release plugin 16.1.0, comparing the local and GitLab checkout states for release/2.0.x and tag v2.0.0. Trace the version calculation used by ./gradlew publish final and verify that both environments derive 2.0.1 from the same branch and tag state.