keploy / keploy/keploy

[feature]: new version is available should be prompted

Open
#2,071 22 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

CLI Enhancement keploy
Dominant language
Go
Stars
18.5k
Forks
2.4k
Avg merge
1d 4h
Merged PRs (30d)
101

Description

Is there an existing feature request for this?
  • I have searched the existing issues
Summary

Similar to zsh shell or any other CLI, once keploy has new release a user should be prompted just once that a new version is available and whether they want to update the version or not. In case the user doesn't want to update and enter [N] or [No], they shouldn't be prompt again in next turn. it should be saved in .keploy file alongside with installation id, and since they have selected no, each time they run keploy there should be a warning log that shows new version and command to update to latest version i.e. keploy update

Why should this be worked on?

Usually, people are not aware that a new keploy version is released, and continue to work on old version till they see the release note or community call.

Repository

keploy

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

Start by locating the CLI version-check and update entry points, then inspect how the .keploy file stores the installation ID. Trace the existing keploy update command and determine how to persist a declined prompt, show the warning on later runs, and avoid prompting more than once.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.