Skip to content

chore(deps): upgrade rustyline 15 → 17 and gate v18+ on dashboard approval#160

Merged
tarotene merged 1 commit into
mainfrom
chore/rustyline-17-pin
May 27, 2026
Merged

chore(deps): upgrade rustyline 15 → 17 and gate v18+ on dashboard approval#160
tarotene merged 1 commit into
mainfrom
chore/rustyline-17-pin

Conversation

@tarotene

@tarotene tarotene commented May 27, 2026

Copy link
Copy Markdown
Owner

Summary

  • tools/telepath/Cargo.toml: rustyline "15""17" (v17.0.2)
  • tools/telepath/Cargo.lock: refreshed via cargo update -p rustyline
  • renovate.json:
    • Restore constraints.rust to "1.88.0" (was incorrectly bumped to "1.95.0" in chore(deps): Update rust Docker tag to v1.95.0 #151 by Renovate itself, causing it to propose MSRV-incompatible updates)
    • Add dependencyDashboardApproval rule for rustyline major bumps (same pattern as probe-rs)

Background

Renovate PR #154 (rustyline 15 → 18) fails the MSRV (1.88) CI gate because rustyline v18 replaces fd-lock with std::fs::File::lock() (upstream PR #909), which was stabilized in Rust 1.89 (tracking issue rust-lang/rust#130994).

Upgrading to v17 instead gives us the v16/v17 improvements (grapheme clusters, SIGINT support, partial-refresh fix) while staying within MSRV 1.88. The rustyline API surface used in tools/telepath/src/cmd/shell.rs (Editor, Helper/Hinter/Highlighter/Validator/Completer, DefaultHistory, ReadlineError) is fully compatible across v15–v17.

Test plan

  • cargo +1.88.0 build passes (MSRV gate reproduced locally)
  • just ci green (fmt-check + clippy + test + host-pty-smoke + mcp-test)
  • CI required checks pass on this PR

Closes #154

🤖 Generated with Claude Code

…roval

- tools/telepath/Cargo.toml: rustyline "15" → "17"
- tools/telepath/Cargo.lock: refresh via cargo update -p rustyline
- renovate.json:
  - restore constraints.rust to "1.88.0" (was incorrectly bumped to "1.95.0"
    in #151, conflicting with AGENTS.md MSRV policy)
  - add packageRule requiring dashboard approval for rustyline major bumps,
    since v18 needs File::lock stabilized in Rust 1.89 (MSRV-incompatible)

Closes the v18 Renovate PR #154; re-evaluate v18 only after a deliberate
MSRV bump.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings May 27, 2026 15:53
@tarotene tarotene enabled auto-merge (squash) May 27, 2026 15:54
@tarotene tarotene disabled auto-merge May 27, 2026 15:54

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Upgrades rustyline from 15 to 17 in tools/telepath to gain v16/v17 improvements while staying within MSRV 1.88 (v18 requires Rust 1.89 due to File::lock stabilization). Also corrects the Renovate constraints.rust value that was incorrectly bumped to 1.95.0 and adds a dashboard-approval rule to prevent future MSRV-incompatible rustyline major bumps.

Changes:

  • Bump rustyline dependency from "15" to "17" and refresh Cargo.lock (pulls in nix 0.30.1, windows-sys 0.60.2).
  • Restore constraints.rust in renovate.json to "1.88.0".
  • Add a Renovate rule gating rustyline major bumps behind Dependency Dashboard approval.

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.

File Description
tools/telepath/Cargo.toml Bumps the optional rustyline dep to v17.
tools/telepath/Cargo.lock Lockfile refresh for rustyline 17.0.2 and transitive deps.
renovate.json Restores Rust MSRV constraint and gates rustyline major updates.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@tarotene tarotene enabled auto-merge (squash) May 27, 2026 15:55
@tarotene tarotene merged commit a327f43 into main May 27, 2026
6 checks passed
@tarotene tarotene deleted the chore/rustyline-17-pin branch May 27, 2026 15:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants