Skip to content

Releases: Sriram-PR/pwsh-neofetch

v1.3.0 - Refactoring & Scripting Support

Choose a tag to compare

@Sriram-PR Sriram-PR released this 16 Dec 10:14

v1.3.0 Release

Major refactoring release focusing on code quality, usability, and PowerShell best practices.

Highlights

  • -AsObject — Get system info as a PowerShell object for scripting and automation
  • -WhatIf/-Confirm — Preview destructive operations before execution
  • Verb-Noun compliance — Renamed to Invoke-Neofetch (alias neofetch preserved)
  • Benchmark removed — Use dedicated tools like CrystalDiskMark instead

What's New

Added

  • -AsObject parameter for structured output (ConvertTo-Json, Export-Csv, etc.)
  • -WhatIf/-Confirm support for -reload and -init
  • ASCII art validation with 20KB size limit
  • Centralized configuration defaults
  • Language-agnostic OneDrive module relocator
  • Expanded Pester test coverage
  • CI version validation

Changed

  • Primary function renamed to Invoke-Neofetch (backward-compatible alias retained)
  • Improved error handling with verbose diagnostics
  • Module no longer exports variables

Removed

  • Benchmark feature (-benchmark parameter)

Fixed

  • Variable scope issue in live graphs
  • Silent error swallowing
  • ASCII art validation fails gracefully with fallback

Security

  • Removed verbose flag from CI to prevent credential exposure

Full Changelog: https://github.com/Sriram-PR/pwsh-neofetch/blob/main/CHANGELOG.md

v1.2.0: Merge pull request #4 from Sriram-PR/feature/live-resource-graph

Choose a tag to compare

@Sriram-PR Sriram-PR released this 11 May 10:08
4e6f60d

🚀 New Features:

  • Introduced Live Resource Usage Graphs:
    • Added a new -live command-line option to display real-time, TUI-based graphs for critical system resources.
    • Graphs include CPU utilization, RAM usage, GPU utilization (NVIDIA only, via nvidia-smi), and VRAM usage (NVIDIA only).
    • Provides a dynamic, btop/htop-like visual overview of system performance directly within the terminal.

✅ How to Update?

For PowerShell Gallery Users:

If you installed pwsh-neofetch from the PowerShell Gallery, update it with:

Update-Module -Name pwsh-neofetch

For GitHub Users:

If you installed pwsh-neofetch manually from GitHub, follow these steps:

1️⃣ Uninstall the current version (run the provided uninstaller script):

.\direct-uninstaller.ps1

2️⃣ Pull the latest version from the repository:

git pull origin main

(or re-clone if needed)

3️⃣ Run the installer script again:

.\direct-installer.ps1

🚀 Direct update via the app is coming soon—stay tuned! 😄

pwsh-neofetch v1.1.2 - Bug Fix release

Choose a tag to compare

@Sriram-PR Sriram-PR released this 05 Mar 19:37

🔧 Fixes & Improvements:

  • Fixed username retrieval issue:
    • In certain cases, when running Windows Terminal with admin rights and providing alternate credentials at a UAC prompt, the $ENV:USERNAME variable could be overwritten as 'SYSTEM' instead of the actual user.
    • The method has been updated to use [System.Environment]::UserName, ensuring the correct username is retrieved regardless of session elevation.

💡 Why This Fix?

  • Prevents incorrect username detection in elevated or credential-switched sessions.
  • Ensures consistent behavior across different terminal and execution contexts.

✅ How to Update?

For PowerShell Gallery Users:

If you installed pwsh-neofetch from the PowerShell Gallery, update it with:

Update-Module -Name pwsh-neofetch

For GitHub Users:

If you installed pwsh-neofetch manually from GitHub, follow these steps:

1️⃣ Uninstall the current version (run the provided uninstaller script):

.\direct-uninstaller.ps1

2️⃣ Pull the latest version from the repository:

git pull origin main

(or re-clone if needed)

3️⃣ Run the installer script again:

.\direct-installer.ps1

🚀 Direct update via the app is coming soon—stay tuned! 😄

Big thanks to @grey0ut for identifying and suggesting a fix for this edge case!

v1.1.1

Choose a tag to compare

@Sriram-PR Sriram-PR released this 01 Mar 12:01
Updated ModuleManifest.