Skip to content

chore(deps): lock file maintenance #681

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

Merged
merged 2 commits into from
Jun 13, 2022

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 12, 2022

Mend Renovate

This PR contains the following updates:

Update Change
lockFileMaintenance All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.


Configuration

📅 Schedule: Branch creation - "before 5am on monday" in timezone Europe/Paris, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Mend Renovate. View repository job log here.

@renovate
Copy link
Contributor Author

renovate bot commented Jun 12, 2022

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: website/yarn.lock
Installing legacy tool yarn v1.22.19
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.

added 1 package in 1s
3.2.1
Usage Error: The nearest package directory (/mnt/renovate/gh/algolia/api-clients-automation/website) doesn't seem to be part of the project declared in /mnt/renovate/gh/algolia/api-clients-automation.

- If /mnt/renovate/gh/algolia/api-clients-automation isn't intended to be a project, remove any yarn.lock and/or package.json file there.
- If /mnt/renovate/gh/algolia/api-clients-automation is intended to be a project, it might be that you forgot to list website in its workspace configuration.
- Finally, if /mnt/renovate/gh/algolia/api-clients-automation is fine and you intend website to be treated as a completely separate project (not even a workspace), create an empty yarn.lock file in it.

$ yarn install [--json] [--immutable] [--immutable-cache] [--check-cache] [--inline-builds] [--mode #0]

@netlify
Copy link

netlify bot commented Jun 12, 2022

Deploy Preview for api-clients-automation failed.

Name Link
🔨 Latest commit 1bba8c2
🔍 Latest deploy log https://app.netlify.com/sites/api-clients-automation/deploys/62a73f0e34e65100085007e1

@algolia-bot
Copy link
Collaborator

algolia-bot commented Jun 12, 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.

@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from 5f1391f to 77bbc31 Compare June 13, 2022 09:28
@millotp millotp merged commit 221b75c into chore/renovateBaseBranch Jun 13, 2022
@millotp millotp deleted the renovate/lock-file-maintenance branch June 13, 2022 13:43
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