Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: fix JavaScript algoliasearch artifacts #561

Merged
merged 1 commit into from
May 25, 2022

Conversation

shortcuts
Copy link
Member

@shortcuts shortcuts commented May 25, 2022

🧭 What and Why

🎟 JIRA Ticket: -

Changes included:

We were restoring the clients twice in the JavaScript algoliasearch job, one included the algoliasearch client itself.

🧪 Test

CI :D

@netlify
Copy link

netlify bot commented May 25, 2022

Deploy Preview for api-clients-automation canceled.

Name Link
🔨 Latest commit 8301429
🔍 Latest deploy log https://app.netlify.com/sites/api-clients-automation/deploys/628e425caa924c0008391d1b

@algolia-bot
Copy link
Collaborator

algolia-bot commented May 25, 2022

✗ The generated branch has been deleted.

If the PR has been merged, you can check the generated code on the main branch.
You can still access the code generated on main via this commit.

@@ -53,27 +53,27 @@ runs:
path: clients/algoliasearch-client-javascript/packages/requester-node-http/

# JavaScript
- name: Download client-javascript-algoliasearch artifact
- name: Download clients-javascript artifact
Copy link
Member Author

@shortcuts shortcuts May 25, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've swapped the order here, as we don't want the js global artifact to override the algoliasearch one, as it happens after

@shortcuts shortcuts self-assigned this May 25, 2022
@shortcuts shortcuts enabled auto-merge (squash) May 25, 2022 14:52
Copy link
Collaborator

@millotp millotp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants