Check the Deno version from .dvmrc

Open
  • Is something wrong?
#67 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@Utkarsh3725 is already working on this.

Since Nov 13, 2026.

  • #73 by @Utkarsh3725 — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
18/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Stale
Tech stack
deno, python
Domain
cli

Research direction

Start in src/devready/checks/runtimes.py, where the RUNTIMES table and the _first_version extractor live, then check explain.py and docs/checks.md for the matching entries. Linked PR #73 is already open against this issue, so read it before starting. Done means a .dvmrc pin of 1.44.0 with Deno 1.40 installed yields one warn showing both versions, and a repo without a Deno pin produces no Deno result, with pytest and ruff passing.

Written by the indexing model from the issue text.

Description

enhancement good first issue help wanted

Problem: Deno projects pin their version in .dvmrc (dvm) or .tool-versions (deno 1.44.0). DevReady does not check Deno at all.

Do:

  • Add a deno row to RUNTIMES in src/devready/checks/runtimes.py (exe deno, args --version, .tool-versions name deno).
  • Pin file: .dvmrc read with the existing _first_version extractor. Id project.deno.pin, miss = warn.
  • .tool-versions support comes for free from the table (project.deno.tool_versions).
  • Add the explain.py entry, a docs/checks.md row, a CHANGELOG line, the README check list mention and unit tests.

Done when:

  • .dvmrc = 1.44.0 with Deno 1.40 installed gives one warn showing both versions.
  • A repo with no Deno pin gets no Deno result.

Done when: see the list above, plus pytest, ruff check and ruff format --check pass.

Notes:

  • Read-only: never execute project files, never echo file contents; only a validated version or spec reaches the report.
  • No network, no new runtime dependencies (Python >= 3.10 stdlib only).
  • Comment below to claim it and I will assign you.
Dominant language
Python
Stars
2
Forks
3
Avg merge
10h 51m
Merged PRs (30d)
40

Getting set up

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 Evalogical-Inc/devReady

All issues in Evalogical-Inc/devReady

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.