Doist / Doist/cli-core

Dependency Dashboard

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

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
0
Forks
0
Avg merge
9h 16m
Merged PRs (30d)
15

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.

Awaiting Schedule

The following updates are awaiting their schedule. To get an update now, click on a checkbox below.

  • chore(deps): update dependency lefthook to v2.1.14
  • chore(deps): update dependency open to v11.0.4
  • 🔐 Create all awaiting schedule PRs at once 🔐

Pending Status Checks

The following updates await pending status checks. To force their creation now, click on a checkbox below.

  • chore(deps): update dependency @types/node to v25.9.8

Open

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

Detected Dependencies

npm (1)
package.json (27)
  • chalk 5.6.2 → [Updates: 6.0.0]
  • yocto-spinner 1.2.2
  • @semantic-release/changelog 6.0.3 → [Updates: 7.0.0]
  • @semantic-release/exec 7.1.0
  • @semantic-release/git 10.0.1 → [Updates: 11.0.1]
  • @types/node 25.9.6 → [Updates: 25.9.8]
  • commander 15.0.0
  • conventional-changelog-conventionalcommits 9.3.1 → [Updates: 10.4.0]
  • lefthook 2.1.12 → [Updates: 2.1.14]
  • marked 18.0.13
  • marked-terminal-renderer 2.2.0
  • oauth4webapi 3.8.8
  • open 11.0.3 → [Updates: 11.0.4]
  • oxfmt 0.62.0 → [Updates: 0.68.0]
  • oxlint 1.77.0 → [Updates: 1.83.0]
  • semantic-release 25.0.9
  • typescript 6.0.3 → [Updates: 7.0.2]
  • vitest 4.1.11 → [Updates: 5.0.0]
  • @napi-rs/keyring 1.3.0 → [Updates: 2.1.0]
  • commander >=14
  • marked >=18
  • marked-terminal-renderer >=2
  • oauth4webapi >=3
  • open >=10
  • vitest >=4.1
  • node >=24
  • npm >=11

  • 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.

Research direction

This is a Renovate-generated dashboard rather than a scoped code task. Start with the linked Renovate Dependency Dashboard documentation and package.json; the listed updates are already open, scheduled, or awaiting status checks. Done would mean selecting a specific dependency update, validating it, and completing its corresponding pull request.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, typescript
Domain
tooling
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.