Dependency Dashboard

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

@LizardByte-bot is already working on this.

Since Apr 15, 2026.

Assessment

This issue has not been assessed yet.

Description

dependencies

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.
View this repository on the Mend.io Web Portal.

Open

The following updates have all been created. To force a retry/rebase of any, click on a checkbox below.

Detected Dependencies

github-actions (8)
.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/discussions-stale.yml
.github/workflows/label-templated-discussions.yml (2)
  • actions/checkout v7.0.1@3d3c42e5aac5ba805825da76410c181273ba90b1
  • actions/github-script v9.0.0@3a2844b7e9c422d3c10d287c895573f7108da1b3
.github/workflows/recategorize-discussions.yml
.github/workflows/rss-monitor.yml (1)
  • git-for-windows/rss-to-issues v0.0.13@99d302b353c4751ca1bda6130fb24934ec12e01e
.github/workflows/rss-notifier.yml (6)
  • actions/github-script v9.0.0@3a2844b7e9c422d3c10d287c895573f7108da1b3
  • actions/github-script v9.0.0@3a2844b7e9c422d3c10d287c895573f7108da1b3
  • sarisia/actions-status-discord v1.16.0@eb045afee445dc055c18d3d90bd0f244fd062708
  • sarisia/actions-status-discord v1.16.0@eb045afee445dc055c18d3d90bd0f244fd062708
  • LizardByte/actions v2026.909.30231@39c468549cfb87ccb917e5e5342e18abc926dc48
  • bluwy/release-for-reddit-action v2@b4ee0e0d64da893e0428912aac5cda675082bd85
npm (1)
package.json (1)
  • jsdom 30.0.1 → [Updates: 30.1.0]
renovate-config (1)
renovate.json
  • Check this box to trigger a request for Renovate to run again on this repository
Dominant language
No language data
Stars
2
Forks
0
Avg merge
2h 37m
Merged PRs (30d)
12

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.

More from LizardByte/community

All issues in LizardByte/community

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.