fix: use project path for API calls again

[fgreinacher]

The numeric project ID is not working for all cases and I don't have the capacity right now to think about a generic solution.

People that have issues with the project path can override CI_PROJECT_PATH for the semantic-release invocation.

Reverts #576

Closes #579

/cc @JedaiRussia @gaborauth

[gaborauth]

I'm sad to hear that, I'm trying to make a private fork for ourself that works for us.

Anyway, thanks for trying (I'm currently on vacation, so I couldn't try it).

[github-actions]

🎉 This PR is included in version 12.0.5 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[glanceon]

I'm sad to hear that, I'm trying to make a private fork for ourself that works for us.

Anyway, thanks for trying (I'm currently on vacation, so I couldn't try it).

Stumbled upon same issue, any updates ?

[gaborauth]

Stumbled upon same issue, any updates ?

It's released and reverted as I know. So, I created a fork, added a configuration option to use the CI_PROJECT_ID and use it internally.

[fgreinacher]

I'd also be open to give #576 another try - I think we just need to make sure to use the numeric project ID only for API resources (below /api/v4) and not for other resources like asset files (https://github.com/semantic-release/gitlab/blob/master/lib/publish.js#L157). Happy to look at a PR for this!