rtk-ai/rtk

feat: version check notification (no auto-update)

Open

#725 opened on Mar 19, 2026

View on GitHub
 (2 comments) (1 reaction) (0 assignees)Rust (48,085 stars) (2,914 forks)batch import
P2-importanteffort-mediumenhancementgood first issue

Description

Show a one-line message when a newer version is available:

[rtk] v0.32.0 available. Run: brew upgrade rtk
  • Check once per day (cache in ~/.local/share/rtk/)
  • Silent on failure (no network = no message)
  • No auto-download, no auto-install
  • Detect install method (brew, cargo, binary) and show the right upgrade command

Contributor guide

Tech stack
rust
Domain
cli
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
RustHTTP clientfile cachingshell commands
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Start by examining the main binary entry point (likely src/main.rs) to understand how commands are dispatched. Add a version check that runs on every command invocation. For HTTP, consider using the `ureq` or `reqwest` crate (check Cargo.toml for existing dependencies). Cache the last check date in a file under ~/.local/share/rtk/version check. To detect the install method, check for common paths (e.g., /usr/local/bin/rtk for brew, ~/.cargo/bin/rtk for cargo) and display the appropriate upgrade command. See existing issue comments and linked discussions for any additional constraints.
feat: version check notification (no auto-update) · rtk-ai/rtk#725 | Good First Issue