Skip to content
Snippets Groups Projects

chore(deps): lock file maintenance

Merged Jednotné přihlášení test requested to merge renovate/lock-file-maintenance into main

This MR contains the following updates:

Update Change
lockFileMaintenance All locks refreshed

:warning: Dependency Lookup Warnings :warning:

Warnings were logged while processing this repo. Please check the logs for more information.

:wrench: This Merge Request updates lock files to use the latest dependency versions.


Configuration

:date: Schedule: Branch creation - "before 3am on Monday" (UTC), Automerge - At any time (no schedule defined).

:vertical_traffic_light: Automerge: Disabled due to failing status checks.

:recycle: Rebasing: Whenever MR is behind base branch, or you tick the rebase/retry checkbox.

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


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

This MR has been generated by Renovate Bot.

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • added 1 deleted label

  • :warning: Artifact update problem

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

    :recycle: 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 MR's title to start with "rebase!" to trigger it manually

    The artifact failure details are included below:

    File name: package-lock.json
    npm ERR! code E404
    npm ERR! 404 Not Found - GET https://registry.npmjs.org/@perun-proxy-aai%2fsemantic-release-proxy-config - Not found
    npm ERR! 404 
    npm ERR! 404  '@perun-proxy-aai/semantic-release-proxy-config@^1.0.3' is not in the npm registry.
    npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
    npm ERR! 404 
    npm ERR! 404 Note that you can also install from a
    npm ERR! 404 tarball, folder, http url, or git url.
    
    npm ERR! A complete log of this run can be found in:
    npm ERR!     /builds/perun-proxy-aai/common/renovate/cache/others/npm/_logs/2022-10-10T00_55_18_380Z-debug.log
    
  • Pavel Břoušek mentioned in commit e0946ca6

    mentioned in commit e0946ca6

  • :tada: This MR is included in version 2.0.0 :tada:

    The release is available on GitLab release.

    Your semantic-release bot :package: :rocket:

Please register or sign in to reply
Loading