chore: bump package version

[shortcuts]

🧭 What and Why

🎟 JIRA Ticket: -

Changes included:

I just released the 0.0.5 version manually, which requires deps versions to be bumped.

This PR also:

• Removes the inlined version from the getting started CDN link.
• Removes duplicate algoliasearch in the scripts CLI.

🧪 Test

CI :D

[netlify]

✅ Deploy Preview for api-clients-automation canceled.

🔨 Explore the source changes: 0a9387d

🔍 Inspect the deploy log: https://app.netlify.com/sites/api-clients-automation/deploys/6238492f0d9c1c000968d385

[shortcuts]

Ah yes, the yarn lock bump should be included the generated code 🤔

[shortcuts]

✗ The generated branch has been deleted.

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

[shortcuts]

._. I did not wanted that

[shortcuts]

I think the codegen CI will fail in that case because the yarn.lock will try to pick remote versions 🤔

Since it's only temporary I won't bother fix it and just push generated code directly. Do you think we will have the issue with the release process @eunjae-lee ?

[eunjae-lee]

I think the codegen CI will fail in that case because the yarn.lock will try to pick remote versions 🤔

Since it's only temporary I won't bother fix it and just push generated code directly. Do you think we will have the issue with the release process @eunjae-lee ?

As I said in DM, I think it should be okay. Let's go! 🚀

[shortcuts]

Checking in #266 if it's really a lock error or race condition as we've seen on the CLI

[shortcuts]

As I said in DM, I think it should be okay. Let's go! 🚀

Actually, after more testing, I found two case where it would have fail:

• Bumping versions like I did here (which shouldn't happen once the release process is done)
• Bumping an utils package and generating code via the CI

It should now all work

[eunjae-lee]

Do you think if there's any way to avoid listing all the paths like this? 🤔

[shortcuts]

Negative patterns does not work properly... So I don't think so :( At least I did not found a better way to both make it clean and working

[eunjae-lee]

I see. It's not a blocker here, but in a separate PR, we should find a way to improve this before it gets too difficult to manage 😬

[shortcuts]

Yep definitely, we also have a task in the backlog to improve the cache key, we should tackle it once we have a bit of time

[eunjae-lee]

• Bumping an utils package and generating code via the CI

I think this will be covered by https://github.com/algolia/api-clients-automation/pull/248/files#diff-15803d489054332c299ad7414e40a62f6034aacdd68eb614d0a920c73de0b08cR191-R206 :)

[shortcuts]

I think this will be covered by https://github.com/algolia/api-clients-automation/pull/248/files#diff-15803d489054332c299ad7414e40a62f6034aacdd68eb614d0a920c73de0b08cR191-R206 :)

But it's done on the CI side, right? So running a yarn install to update the lock file would've throw anyway