Module updates 

Lightweight update discovery and update commands.

Startup checks are deliberately best-effort: callers decide when to run them, each registry request uses a short timeout, and cached values are retained only as a fallback for temporary registry failures.

Structs

UpdateNotice

UpdateReport

UpdateWarning

Functions

check_package_startup_with_resources

Package-only compatibility wrapper using the built-in npm executable and an isolated working directory.

check_package_startup_with_resources_and_npm_command_in_cwd

Check only npm, Git, and native Rust packages. This is the package half of check_rpi_startup and is safe to run concurrently with it.

check_rpi_startup

Check only the rpi release. Callers can render this report independently so slow package-manager subprocesses never delay the self-update notice.

check_startup

Perform a best-effort check with Pi package discovery disabled.

check_startup_with_package_resources

Perform a best-effort startup check, using cached values only when a fresh request fails.

check_startup_with_package_resources_and_npm_command

Perform startup discovery using the effective trusted npmCommand argv. Keeping the command explicit prevents a project wrapper from being used before its trust decision has been applied.

check_startup_with_package_resources_and_npm_command_in_cwd

Perform startup discovery with an explicitly trust-gated npm working directory. None runs every npm lookup in a fresh isolated directory; callers may supply the project cwd only after that project is trusted.

is_newer

Compare complete semantic versions, including prerelease precedence.

print_startup_notices

run_self_update

Update the installed rpi CLI through its documented crates.io install path. Windows stages first because a running executable cannot replace itself; other platforms retain Cargo’s direct replacement behavior.