chore(ci): rename version tag

[eunjae-lee]

🧭 What and Why

https://algolia.atlassian.net/browse/APIC-450

Changes included:

The release process creates tags like v5.0.0 for release. However, actually our each repository doesn't have v prefix at all.

• https://github.com/algolia/algoliasearch-client-javascript/tags
• https://github.com/algolia/algoliasearch-client-java-2/tags
• https://github.com/algolia/algoliasearch-client-php/tags

So this PR renames the tag format to be aligned with the existing tags.

(Also, on the PHP repo, release is triggered by a git tag, and the format matters.)

🧪 Test

[netlify]

✅ Deploy Preview for api-clients-automation canceled.

Name	Link
🔨 Latest commit	a8531e3
🔍 Latest deploy log	https://app.netlify.com/sites/api-clients-automation/deploys/626a58af3715c1000889f50b

[algolia-bot]

✗ The generated branch has been deleted.

If the PR has been merged, you can check the generated code on the main branch.

[shortcuts]

There is no other occurrences? I thought I saw it elsewhere 🤔

[eunjae-lee]

There is not other occurences? I thought I saw it elsewhere 🤔

In InstantSearch, we use vx.y.z.

Edit: I just confirmed only algoliasearch-client-go has v prefix 😅 I'm going to update this PR. Wait a sec!

[shortcuts]

Ah it's in the GitHub actions

edit: the commit are sent with the v prefix
edit2: the docs also have some mentions

[eunjae-lee]

Ah it's in the GitHub actions

edit: the commit are sent with the v prefix

We can keep v for the commit message, tho?

[shortcuts]

We can keep v for the commit message, tho?

It's just that we will have difference in naming here and there, like the release issue will also have the v while we publish the tag without it

[shortcuts]

Like those they won't work if we keep the v, no?

https://github.com/algolia/api-clients-automation/blob/main/scripts/release/process-release.ts#L162-L164

[eunjae-lee]

Like those they won't work if we keep the v, no?

https://github.com/algolia/api-clients-automation/blob/main/scripts/release/process-release.ts#L162-L164

Ah that's a good catch. I'll revisit the two whole scripts and check what needs to be changed.

[shortcuts]

Looks good!