chore: run JavaScript algoliasearch after other clients #266
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
✔️ Deploy Preview for api-clients-automation canceled. 🔨 Explore the source changes: 7503b99 🔍 Inspect the deploy log: https://app.netlify.com/sites/api-clients-automation/deploys/6234a1d7b2c3150008ea1948 |
|
✗ The generated branch has been deleted. If the PR has been merged, you can check the generated code on the |
shortcuts
force-pushed
the
chore/ci-algoliasearch-race
branch
5 times, most recently
from
ff9bae7 to
aec1e76
Compare
shortcuts
force-pushed
the
chore/ci-algoliasearch-race
branch
from
aec1e76 to
7503b99
Compare
shortcuts
requested review from
a team,
eunjae-lee and
damcou
and removed request for
a team
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🧭 What and Why
🎟 JIRA Ticket: -
Changes included:
Follow up of #264
There was multiple issues in this PR:
yarn.lockdistfolder did not worked, I've went with a verbose solutionalgoliasearchdepends on other client, I've put the step after the generated client buldsWhy
The bump of generated client shouldn't happen out of the release process, but will still happen when we bump a utils package. This PR ensures that it can be done via the CI without touching the
yarn.locketc.🧪 Test
CI :D