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(dependency): lock file maintenance #168

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 5, 2023

This PR contains the following updates:

Update Change
lockFileMaintenance All locks refreshed

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

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


Configuration

📅 Schedule: Branch creation - "before 4am on monday" in timezone Europe/Moscow, 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, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies label Mar 5, 2023
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from 9350ea4 to 27cedb1 Compare March 11, 2023 09:57
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from 1a9bb1a to 5ddf9ef Compare April 15, 2023 12:54
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from ef45692 to bb1bc24 Compare May 31, 2023 22:09
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from bb1bc24 to 336193f Compare August 28, 2023 20:39
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from e602f1d to 55947c0 Compare September 5, 2023 14:35
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from 0b5ba8a to b189715 Compare October 9, 2023 19:30
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from b189715 to dacfdcc Compare December 3, 2023 15:20
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from dacfdcc to 455225e Compare February 29, 2024 02:46
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from 455225e to cc550dc Compare February 29, 2024 02:49
Copy link
Contributor Author

renovate bot commented May 28, 2024

⚠️ 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: pnpm-lock.yaml
Scope: all 16 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
/tmp/renovate/repos/github/grammyjs/storages/packages/file:
 ERR_PNPM_FETCH_404  GET https://registry.npmjs.org/@grammyjs%2Fstorage-utils: Not Found - 404

This error happened while installing a direct dependency of /tmp/renovate/repos/github/grammyjs/storages/packages/file

@grammyjs/storage-utils is not in the npm registry, or you have no permission to fetch it.

No authorization header was set for the request.

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

Successfully merging this pull request may close these issues.

0 participants