Skip to main content
The upgrade command checks for and installs the latest version of Pensar Apex.

Syntax

Alias: pensar update

Description

The upgrade command:
  1. Checks your current Pensar version
  2. Queries GitHub for the latest release
  3. Downloads and installs the update if available
  4. Verifies the installation
The upgrade process is interactive and will prompt you before making changes.

No Options Required

The upgrade command runs without any flags or options:
Or using the alias:

Examples

Check for Updates

Run the upgrade command to check for new versions:
Output (when update available):
Output (when up to date):

Automatic Update

Accept the update prompt to install:

Decline Update

Skip the update by answering ‘n’:

Using the Alias

The update command works identically:

Update Process

The upgrade follows these steps:

Installation Locations

Pensar is installed to different locations based on your installation method:
Default location: ~/.pensar/bin/pensarThe upgrade command updates the binary in place:
Make sure this is in your PATH:

Version Checking

Check your current version without upgrading:
Output:

Release Channels

Pensar has two release channels:

Stable (Default)

The upgrade command installs stable releases:
Stable releases are:
  • Thoroughly tested
  • Production-ready
  • Recommended for most users

Canary (Bleeding Edge)

For the latest features (may be unstable):
Canary releases may contain bugs and breaking changes. Only use for testing or development.

Rollback

If you need to rollback to a previous version:

Method 1: Specific Version

Method 2: Previous Version

Automatic Updates

Pensar checks for updates automatically:
  • TUI: Shows notification on launch if update available
  • CLI: Displays update message after command completion

Disable Update Check

To disable automatic update checks:

Update Notifications

When an update is available, you’ll see a notification:

Exit Codes

Use Cases

Regular Maintenance

Keep Pensar up to date:

Before Critical Pentests

Ensure you have the latest security improvements:

CI/CD Pipeline

Always use the latest version in automation:

Development Testing

Test against the latest version:

Troubleshooting

Download Fails

If the download fails:

Permission Denied

If installation fails with permission errors:

Version Not Changing

If pensar version shows old version after upgrade:

Network Issues

If you’re behind a proxy or firewall:

Rate Limiting

GitHub API rate limits may affect update checks:

Configuration

Upgrade behavior can be configured in ~/.pensar/config.json:
boolean
default:"true"
Enable automatic update checking
boolean
default:"false"
Automatically download updates (still requires confirmation to install)
string
default:"stable"
Release channel: stable or canary
boolean
default:"true"
Show update notifications when launching Pensar
  • doctor - Verify system configuration after upgrade
  • pensar - Launch TUI with updated version
  • version - Check current version

Next Steps

Changelog

View all release notes and changes

GitHub Releases

Download specific versions manually