Let me see the release notes before taking an update

Open
#2,546 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
desktop, release

Research direction

No files, tests, or entry points are named. Start by locating the update/install flow and its release-note handling; before coding, get a decision on whether the intended outcome is preview and skip support, restarting sessions, or both, then define completion criteria with maintainers.

Written by the indexing model from the issue text.

Description

enhancement triaged
Discord username (optional)

tarwich#6534

Describe the solution you'd like?
I would like a better "install updates" experience. 

- One solution would be to let me read the release notes and choose to skip the update
- Another solution would be to have the option to restart all the processes that were running
Is your feature request related to a problem? Please describe.
First let me say Warp is cool.

It's frustrating to see "UPDATE AVAILABLE!!!!OMGTHEWORLDISENDING", then click it and find a very small update like "Changed fonts". After taking the update, I have to restart all my terminal sessions to all my remote servers. Mosh helps with this, but it's still something I have to restart in several different panes.
Additional context

I run lots of sessions for managing remote servers. I like to have the windows open. I also like to take security updates, because... security. But if the updates are minor, can I skip them?

Partially related to #1723

How important is this feature to you?

3

Warp Internal (ignore) - linear-label:770f6576-d6c0-4e4f-a259-fc64b5156087

None

Dominant language
Rust
Stars
65.1k
Forks
5.6k
PR merge metrics
PR metrics pending

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.

More from warpdotdev/warp

All issues in warpdotdev/warp

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.