Keeping the Proxmox host itself up to date is the most common maintenance task. Today you have to log in to the node or open the web UI to see whether updates are waiting.
Proposal
A node screen, or a line in the main frame, shows the number of pending package updates per node and lists them (package, current version, new version).
Read-only to start with. Running the upgrade itself stays out of scope: it belongs in a shell on the node, which t-style SSH could open later.
cv4pve-cli (2.4.0)
get node packages <node>
get node apt. Check its subcommands, for example update/changelog.
## Why
Keeping the Proxmox host itself up to date is the most common maintenance task. Today you have to log in to the node or open the web UI to see whether updates are waiting.
## Proposal
- A node screen, or a line in the main frame, shows the number of pending package updates per node and lists them (package, current version, new version).
- Read-only to start with. Running the upgrade itself stays out of scope: it belongs in a shell on the node, which `t`-style SSH could open later.
## cv4pve-cli (2.4.0)
- `get node packages <node>`
- `get node apt`. Check its subcommands, for example update/changelog.
## Done when
- The node update list is shown.
- Tests are written first.
- A read-only live check passes.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Why
Keeping the Proxmox host itself up to date is the most common maintenance task. Today you have to log in to the node or open the web UI to see whether updates are waiting.
Proposal
t-style SSH could open later.cv4pve-cli (2.4.0)
get node packages <node>get node apt. Check its subcommands, for example update/changelog.Done when
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com