Dependency Dashboard
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 22
- Forks
- 19
- Avg merge
- 18h 31m
- Merged PRs (30d)
- 50
Description
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.
Abandoned Dependencies
The following dependencies have not received updates for an extended period and may be unmaintained.
[!NOTE]
Packages are marked as abandoned when they exceed theabandonmentThresholdsince their last release. Unlike deprecated packages with official notices, abandonment is detected by release inactivity.
View abandoned dependencies (1)
| Datasource | Package | Last Updated |
|---|---|---|
| npm | @bcoe/v8-coverage | 2025-01-15 |
Awaiting Schedule
The following updates are awaiting their schedule. To get an update now, click on a checkbox below.
- Lock file maintenance
Pending Status Checks
The following updates await pending status checks. To force their creation now, click on a checkbox below.
- Update dependency @types/node to v24.13.6
Open
The following updates have all been created. To force a retry/rebase of any, click on a checkbox below.
- Update TryGhost packages (
@tryghost/content-api,@tryghost/errors,@tryghost/pretty-cli) - Update pnpm to v12
- Update vitest monorepo to v5 (
@vitest/coverage-v8,vitest) - Click on this checkbox to rebase all open PRs at once
Detected Dependencies
github-actions (3)
.github/workflows/live-ghost-content-smoke.yml (3)
actions/checkout v7.0.1@3d3c42e5aac5ba805825da76410c181273ba90b1pnpm/action-setup v6.1.0@ea17c68df8912ef543352723c149a84f56e3d413actions/setup-node v7.0.0@820762786026740c76f36085b0efc47a31fe5020.github/workflows/publish.yml (3)
actions/checkout v7.0.1@3d3c42e5aac5ba805825da76410c181273ba90b1pnpm/action-setup v6.1.0@ea17c68df8912ef543352723c149a84f56e3d413actions/setup-node v7.0.0@820762786026740c76f36085b0efc47a31fe5020.github/workflows/test.yml (3)
actions/checkout v7.0.1@3d3c42e5aac5ba805825da76410c181273ba90b1pnpm/action-setup v6.1.0@ea17c68df8912ef543352723c149a84f56e3d413actions/setup-node v7.0.0@820762786026740c76f36085b0efc47a31fe5020
npm (7)
package.json (10)
@bcoe/v8-coverage 1.0.2@nx/js 23.2.1@vitest/coverage-v8 4.1.11→ [Updates:5.0.1]nx 23.2.1oxfmt 0.68.0oxlint 1.83.0vite 8.3.0vitest 4.1.11→ [Updates:5.0.1]node >=24pnpm 11.27.0+sha512.ad12821463bb143295f1fa3ecde77a6b9b97a7990386da800ff57bffc3964dc64b7b1c7559d5dbe5c337aea659ed9c8937d4370bd198ca2009bc6fa0249808e7→ [Updates:12.4.2]packages/algolia-fragmenter/package.json (3)
@types/node 24.13.5→ [Updates:24.13.6]typescript 7.0.2node >=24packages/algolia-html-extractor/package.json (4)
parse5 8.0.1@types/node 24.13.5→ [Updates:24.13.6]typescript 7.0.2node >=24packages/algolia-indexer/package.json (2)
algoliasearch 5.59.0node >=24packages/algolia-netlify/package.json (6)
algoliasearch 5.59.0@types/node 24.13.5→ [Updates:24.13.6]esbuild 0.28.2netlify-cli 27.8.0typescript 7.0.2node >=24packages/algolia/package.json (7)
@tryghost/content-api 1.12.10→ [Updates:1.12.11]@tryghost/errors 3.3.13→ [Updates:3.3.14]@tryghost/pretty-cli 3.3.13→ [Updates:3.3.14]fs-extra 11.4.0@types/node 24.13.5→ [Updates:24.13.6]typescript 7.0.2node >=24pnpm-workspace.yaml (1)
sharp ^0.35.3
nvm (2)
.nvmrc (1)
node 24packages/algolia-netlify/.nvmrc (1)
node 24
renovate-config (1)
renovate.json
- Check this box to trigger a request for Renovate to run again on this repository
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
This is an automated Renovate dashboard rather than a scoped task. Review package.json, the listed package manifests, pnpm-workspace.yaml, .nvmrc files, GitHub workflow files, and the linked pull requests to determine which dependency update remains actionable. Done would require a specifically selected update with its checks passing, but the issue does not define one.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, nodejs, typescript
- Domain
- build-system, devops
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100