v2.5.17

Changelog and Bug Fixes – VenvHub Pro v2.5.17

This release focuses on resolving bugs related to coordination with the VS Code development environment and local package management (Linker). Below is an overview of the key changes you will notice during daily use:

Selective Task Scanning:

Where the change occurred: In the process of transferring tasks and keybindings to VS Code.
How it works now: The application no longer scans the entire local packages root folder upon saving. It analyzes only those modules that are actively checked for the current environment. This prevents tasks from unrelated (unlinked) projects from cluttering your active editor.

Consistent Task Removal Upon Deactivation (Brutal Check):

Where the change occurred: In the package removal logic.
How it works now: When unchecking (deactivating) a package, the program reads its configuration and safely removes the associated tasks and keybindings from VS Code without affecting any tasks you created manually in the editor.

Recovery System for Manually Deleted Folders:

Where the change occurred: Through the introduction of a tracking helper file (.vscode/venvhub_tracker.json).
How it works now: If you delete a local package folder manually via File Explorer without unchecking it first in the application, the program will not halt. It utilizes the information from the tracking helper file (the "receipt") to safely identify and clean up the orphaned tasks from the VS Code configuration.

Task Alignment During Environment Switching:

Where the change occurred: In the default environment activation service (clicking the "Star" in the Manager).
How it works now: Previously, when switching to another Venv, the program only updated the Python interpreter paths, leaving tasks from the previous environment behind in the editor. As of version 2.5.17, changing the default Venv automatically aligns all associated tasks and keybindings in VS Code (deregistering old ones and writing new ones).

Automatic Cleanup of Empty Configuration Files:

Where the change occurred: In the saving of configurations inside .vscode.
How it works now: If no active tasks or keybindings remain in tasks.json or keybindings.json after uninstalling a package or switching the Venv, the application physically deletes these empty files (including the tracking helper file) from the disk, preventing the accumulation of empty configuration files in the project folder.

Global Support and Integrity Verification for UV (Astral):

Where the change occurred: In the asynchronous workers managing bulk and individual package actions (PipWorkerAllUpdate, PipCommandWorker, and PipWorker).
How it works now: If the UV manager is active in your settings, the program automatically runs a background uv check after every package installation, uninstallation, or upgrade. If incompatible versions are identified, it automatically attempts a recovery (performing version downgrades or reinstalling exact compatible versions).

Full UV Integration for Quick Actions from the Mini-Bar:

Where the change occurred: In the quick installer of the Mini-Bar and Quick Settings.
How it works now: Quick package installation initiated directly from the mini-panel now respects the active UV manager and executes post-installation dependency checking and conflict resolution.

Legacy Codebase Cleanup:

Where the change occurred: Removal of redundant files (update_all.py and install.py).
How it works now: Outdated, unused scripts that did not support the UV installer and bypassed the unified dispatcher have been completely removed, ensuring a cleaner codebase and faster execution of the package management core.