Dependency Dashboard

Open
#3 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
github-actions, nodejs, typescript

Research direction

Review .github/workflows/ci.yaml and package.json alongside the Dependency Dashboard documentation; the listed update pull requests (#74, #85, #87–93) are the entry points. No unclaimed change is described here, so first confirm which dependency update remains needed; completion would require validating and merging that selected update.

Written by the indexing model from the issue text.

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.

Open

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

Detected Dependencies

github-actions (1)
.github/workflows/ci.yaml (5)
  • actions/checkout v7
  • pnpm/action-setup v6
  • actions/setup-node v7
  • ubuntu 26.04
  • node 26
npm (2)
package.json (10)
  • @tmcp/adapter-valibot ^0.1.6
  • @tmcp/transport-stdio ^0.5.0 → [Updates: lock file @ 0.5.2]
  • tmcp ^1.20.0
  • valibot ^1.5.0
  • @changesets/cli ^3.0.3
  • @types/node 26.6.6
  • typescript ^7.0.2
  • vite-plus 1.6.0 → [Updates: 1.7.0]
  • node >=22.0.0
  • pnpm 12.18.0 → [Updates: 12.21.0]
pnpm-workspace.yaml (1)
  • vite@* 1.6.0 → [Updates: 8.3.8000]

  • Check this box to trigger a request for Renovate to run again on this repository
Dominant language
TypeScript
Stars
589
Forks
82
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.