LizardByte / LizardByte/build-deps

Dependency Dashboard

Open
#659 0 comments 0 reactions 1 assignee View on GitHub

@LizardByte-bot is already working on this.

Since Apr 15, 2026.

dependencies
Dominant language
CMake
Stars
8
Forks
50
Avg merge
8h 6m
Merged PRs (30d)
17

Description

This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.
[View this repository on the Mend.io Web Portal](https://developer.mend.io/github/LizardByte/build-deps).

This repository currently has no open or pending branches.

## Detected Dependencies

github-actions (4)

.github/workflows/_codeql.yml (1)

- `LizardByte/.github master`

.github/workflows/_common-lint.yml (1)

- `LizardByte/.github master`

.github/workflows/_top-issues.yml (1)

- `LizardByte/.github master`

.github/workflows/ci.yml (9)

- `actions/checkout v7.0.1@3d3c42e5aac5ba805825da76410c181273ba90b1`
- `LizardByte/actions v2026.909.30231@39c468549cfb87ccb917e5e5342e18abc926dc48`
- `laverdet/alpine-arm64 v1.0.0@7f0f72ee2f71eb2324e5888e8b6e42b1b53e6160`
- `actions/checkout v7.0.1@3d3c42e5aac5ba805825da76410c181273ba90b1`
- `msys2/setup-msys2 v2.32.0@66cd2cce69caa17b53920067426061ca1de3a884`
- `vmactions/freebsd-vm v1.5.7@4469451fe39bee80be4066836c5170362e9349f3`
- `actions/upload-artifact v7.0.1@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a`
- `actions/download-artifact v8.0.1@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c`
- `LizardByte/actions v2026.909.30231@39c468549cfb87ccb917e5e5342e18abc926dc48`

regex (1)

package-lock.cmake (5)

- `FFmpeg/nv-codec-headers n11.0.10.3`
- `FFmpeg/nv-codec-headers n12.0.16.2`
- `FFmpeg/nv-codec-headers n13.0.19.1`
- `FFmpeg/nv-codec-headers n13.1.15.0`
- `intel/libva 2.24.1`

renovate-config (1)

renovate.json

---

- [ ] Check this box to trigger a request for Renovate to run again on this repository

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.