Release v1.0.4 — The Guardian Protocol

Release v1.0.4 — The Guardian Protocol

Modern tools promise speed, but often just accelerate environment destruction. This release introduces the ultimate undo button for your Python workspace: omnipkg revert.

omnipkg now functions as a guardian for your environment. After every successful omnipkg operation, it automatically saves a “last known good” snapshot. If you ever make a mistake with another package manager, omnipkg can now restore your environment to its last pristine state in seconds.

✨ Highlights

• ↩️ Introducing omnipkg revert: A new top-level command to instantly restore your environment from damage.
• 📸 Automatic Environment Snapshots: Every successful omnipkg operation now automatically creates a recovery point.
• ❤️‍🩹 Self-Healing Workflow: omnipkg is no longer just a preventative tool; it can now actively repair damage done by others.

💥 The Proof: Reverting a High-Speed Disaster

Let’s see it in action.

Step 1: Create a Complex “Last Known Good” State

First, we'll demonstrate omnipkg's core intelligence. We'll install an older version of a package, forcing the Downgrade Protection to activate and create our snapshot.

# We ask omnipkg to install an older version over a newer one.
$ omnipkg install flask-login==0.4.1```
Instead of failing, `omnipkg` performs surgery:
```bash
# It detects the conflict and activates its core feature.
🛡️  DOWNGRADE PROTECTION ACTIVATED!
    -> Fixing downgrade: flask-login from v0.6.3 to v0.4.1
🫧 Creating isolated bubble for flask-login v0.4.1
    📊 Space efficiency: 55.5% saved.
    🔄 Restoring 'flask-login' to safe version v0.6.3 in main environment...
✅ Environment protection complete!

# Finally, it saves the perfect state as our recovery point.
📸 Saving snapshot of the current environment as 'last known good'...
   ✅ Snapshot saved.

At the end of this operation, our environment is pristine: flask-login==0.6.3 is active, and the older 0.4.1 is safely isolated in a bubble.

Step 2: The “Accident” with uv

Now, we simulate a user accidentally using uv to downgrade the package.

$ uv pip install flask-login==0.4.1
Uninstalled 1 package in 0.41ms
Installed 1 package in 2ms
 - flask-login==0.6.3
 + flask-login==0.4.1

# Fast? Yes. Correct? No. The environment is now broken.

Step 3: The Guardian Protocol

With the environment in a damaged state, we call on omnipkg to fix it.

$ omnipkg revert

# omnipkg loads the snapshot and instantly knows what's wrong.
⚖️  Comparing current environment to the last known good snapshot...

📝 The following actions will be taken to restore the environment:
  - Fix Version: flask-login==0.6.3

🤔 Are you sure you want to proceed? (y/N): y

# It executes the plan with surgical precision.
🚀 Starting revert operation...
# ... (omnipkg uninstalls the wrong version and installs the right one) ...
✅ Environment successfully reverted to the last known good state.

The Final State: Perfection

A final check confirms the environment has been perfectly restored.

$ omnipkg info flask-login

📋 KEY DATA for 'flask-login':
----------------------------------------
🎯 Active Version: 0.6.3
🫧 Bubbled Versions: 0.4.1

The magic is in the details: omnipkg not only restored the correct active version (0.6.3) but also ensured the bubbled version (0.4.1) was still perfectly preserved. It has a complete memory of the ideal state, ensuring your workflow continues uninterrupted.

---

This isn’t just a new feature; it’s peace of mind. You can now work, knowing that omnipkg always has your back.

Release v1.0.3 — The Sequential Synthesizer

This release elevates omnipkg from a powerful tool to a true dependency orchestration engine. We've introduced a revolutionary installation logic capable of handling multiple, conflicting package versions in a single command—a task that instantly crashes other package managers.

✨ Highlights

• Sequential Installation Engine: Intelligently processes conflicting requirements (e.g., torch==2.7.1 torch==2.0.0) synchronously, mimicking how a human expert would solve the problem.
• Intelligent Task Reordering: Automatically sorts packages to install newest versions first, ensuring downgrade protection and bubbling are triggered with surgical precision.
• Atomic Environment Cleansing: A core design principle demonstrated below, where the environment is surgically prepared before complex operations.

💥 The Proof: Orchestrating an "Impossible" Install

To prove the power of this new engine, we'll do something no other tool can: install two conflicting versions of PyTorch in the "wrong" order.

Step 1: Prepare the Environment

As a prerequisite, omnipkg first ensures a clean state. This includes clearing out any residual packages or tools that might interfere.

# As a prerequisite, we first uninstall any unnecessary tools.
$ omnipkg uninstall uv -y
🗑️ Uninstalling 'uv' from main environment...
Successfully uninstalled uv-0.7.14
🗑️ Deleting bubble: uv-0.7.13
✅ Uninstallation complete.

# Next, we purge all existing torch versions for a clean slate.
$ omnipkg uninstall torch -y
🗑️ Uninstalling 'torch' from main environment...
🗑️ Deleting bubble: torch-2.7.0
🗑️ Deleting bubble: torch-2.0.1
🗑️ Deleting bubble: torch-2.0.0
✅ Uninstallation complete.

Step 2: Request the Impossible

We now ask omnipkg to install two conflicting torch versions, providing them in the logically incorrect order (older version first).

$ omnipkg install torch==2.0.0 torch==2.7.1

Step 3: Watch the Magic

omnipkg doesn't fail. It orchestrates.

# It intelligently reorders the user's request for optimal execution.
🔄 Reordered packages for optimal installation: torch==2.7.1, torch==2.0.0

────────────────────────────────────────────────────────────
📦 Processing: torch==2.7.1
# ... (Installation of the newest version proceeds) ...
✅ No downgrades detected. Installation completed safely.
🧠 Updating knowledge base...

────────────────────────────────────────────────────────────
📦 Processing: torch==2.0.0
# ... (pip attempts to install 2.0.0 over 2.7.1) ...
🔬 Analyzing post-installation changes...

# The engine detects the downgrade and activates its core feature.
🛡️  DOWNGRADE PROTECTION ACTIVATED!
    -> Fixing downgrade: torch from v2.7.1 to v2.0.0
🫧 Creating isolated bubble for torch v2.0.0
    # ... (Bubble created with 33.4% space saved via deduplication) ...
    🔄 Restoring 'torch' to safe version v2.7.1 in main environment...
✅ Environment protection complete!

The Final State: Perfect Isolation

The operation completes, leaving a pristine main environment and a perfectly isolated older version, ready for use.

$ omnipkg info torch

📋 KEY DATA for 'torch':
----------------------------------------
🎯 Active Version: 2.7.1
🫧 Bubbled Versions: 2.0.0

---

"Other tools attempt dependency resolution.
Omnipkg orchestrates dependency symphonies."

---

🔥 Get It Now:
pip install omnipkg==1.0.3

omnipkg v1.0.2 - Added Uninstall Feature

🧨 Release v1.0.2 — “Uninstalled with Prejudice”

✨ Highlights

• Introducing omnipkg uninstall: A new, intelligent command that ensures complete and thorough removal of packages and their associated metadata. This isn’t just pip uninstall; this is surgical removal—dependencies, cached data, the entire footprint.
• Redis-Powered Metadata Purge: omnipkg now leverages its Redis knowledge base to precisely identify and remove all traces of a package, including “bubble” versions and cached data. Zero-residue cleanup that no other Python tool even attempts.
• Automatic Version Detection: No need to specify which version to remove. omnipkg uninstall automatically detects all installed versions of a package (both active and bubbled) and offers to clean them all.

💥 Real-World Example: Erasing uv

Let’s see this in action with uv. When we downgraded uv from 0.8.5 to 0.7.14, omnipkg cleverly created an isolated “bubble” to protect our main environment. Many package managers would leave behind an orphan environment or an incomplete mess, but omnipkg handles this gracefully.

First, let’s remove the primary installation:

$ omnipkg uninstall uv==0.8.5

Processing uninstall for: uv==0.8.5
Found 1 installation(s) to remove:
  - v0.8.5 (active)
🤔 Are you sure you want to proceed? (y/N): y
🗑️ Uninstalling 'uv' from main environment...
  Successfully uninstalled uv-0.8.5

✅ Uninstallation complete.

Now, the main environment is clean, but the isolated 0.7.14 bubble still exists. A quick omnipkg status shows us the clean separation:

$ omnipkg status
...
📦 Isolated Package Versions (85):
  - 📁 uv-0.7.14 (0.0 MB)
...

Notice the uv-0.7.14 bubble. Now, let’s see what a truly thorough uninstallation looks like. We target the bubble itself, and omnipkg knows exactly what to do:

$ omnipkg uninstall uv==0.7.14

Processing uninstall for: uv==0.7.14
Found 1 installation(s) to remove:
  - v0.7.14 (bubble)
🤔 Are you sure you want to proceed? (y/N): y
🗑️ Deleting bubble: uv-0.7.14
✅ Uninstallation complete.

Just like that, uv is completely gone—no files, no metadata, no residue. We don’t just uninstall a file. We delete the entire bubble, its metadata, and all of its dependencies, ensuring zero-residue cleanup.

🧠 Under the Hood

The new uninstall command is now fully integrated with our memory display, status reporting, and Redis knowledge base. This ensures that when you remove a package, you are truly removing it from the entire omnipkg ecosystem, whether it was in the main environment or an isolated bubble.

• Fully integrated with Redis memory display
• Synchronized with status, info, and activate commands
• Bubble cleaner handles nested dependencies
• Prevents orphan bubbles, ghost data, and partial states

omnipkg v1.0.1 - Pushing updated README to PyPi.

Pushing README changes to PyPi.

omnipkg v1.0.0: The End of Dependency Hell

omnipkg v1.0.0: The End of Dependency Hell

After extensive development and rigorous validation, omnipkg v1.0.0 is now publicly available.

This isn't just another package manager. It's a fundamental paradigm shift built on one revolutionary premise: you should never have to choose between package versions again.

The Persistent Problem We've Solved

Python developers have long struggled with dependency gridlock. Version conflicts force impossible choices: break your environment or abandon needed packages. Virtual environments create fragmentation and maintenance overhead.

omnipkg eliminates these compromises entirely.

How It Works: Bubble Isolation Technology

omnipkg introduces package bubbling - a breakthrough isolation system that allows conflicting versions to coexist seamlessly. When you install a conflicting package, omnipkg automatically:

1. Detects conflicts via real-time environment snapshots
2. Creates secure bubbles for problematic versions
3. Performs integrity checks using SHA-256 hashing
4. Deduplicates dependencies (60% average space savings)
5. Maintains full functionality of all versions

The result? 14+ GB of packages coexisting peacefully - including multiple PyTorch versions and ML stacks - where traditional tools fail.

Performance Benchmarks

• Knowledge base updates: 8 packages/second from scratch
• Delta caching: Near-instant subsequent operations
• Runtime switching: Faster than terminal streams
• Storage efficiency: 60% average savings via SHA-256 deduplication
• Full validation: Complete NumPy/SciPy install/run/swap in <30s
• Speed: Outperforms raw pip with full protection

Making the Impossible Achievable

🔬 Live Example: Safe Flask-Login Downgrade

# Install conflicting flask-login version
$ omnipkg install flask-login==0.4.1

📸 Taking LIVE pre-installation snapshot...
    - Found 545 packages

🛡️  DOWNGRADE PROTECTION ACTIVATED!
-> Detected conflict: flask-login v0.6.3 → v0.4.1
🫧 Creating bubble for flask-login v0.4.1
    -> Strategy 1: pip dry-run...
    -> Strategy 2: PyPI API...
    ✅ Dependencies resolved via PyPI API
📦 Installing to temporary location...
🧹 Creating deduplicated bubble...
⚡️ Loading hash index from cache...
📈 Loaded 203,032 file hashes
⚠️  Native isolation: MarkupSafe
✅ Bubble created: 151 files copied, 188 deduplicated
📊 Space saved: 55.5%
🔄 Restoring flask-login v0.6.3...

✅ Environment secured!

# Verify final state
$ omnipkg info flask-login

📋 flask-login STATUS:
----------------------------------------
🎯 Active: 0.6.3 (protected)
🫧 Available: 0.4.1
📊 Space Saved: 55.5% (188 files deduplicated)
🔄 Switch: omnipkg activate flask-login==0.4.1

You now have both versions available without virtual environments or conflicts.

Need stronger proof? Witness our ultimate validation.

🔥 Ultimate Validation: NumPy & SciPy Version Matrix

(omnipkg_heaven) $ omnipkg validate

============================================================
  🚀 omnipkg Ultimate Validation Suite
============================================================
⚠️ Downloads several hundred MB (takes 2-5 minutes)

Run validation? (y/n): y

============================================================
  🚀 PHASE 1: Clean Environment Preparation
============================================================
...
Successfully installed numpy-1.26.4

🔬 Analyzing changes...

🛡️  PROTECTION ACTIVATED!
    -> Handling: numpy v2.3.2 → v1.26.4
🫧 Creating bubble for numpy v1.26.4
    ...
    ✅ Bubble created: 1407 files
    📊 Space saved: 0.0%
    🔄 Restoring numpy v2.3.2...

✅ Environment secured!

============================================================
  🚀 PHASE 2: Multi-Version Bubble Creation
============================================================
...
--- Creating numpy==1.24.3 bubble ---
🫧 Isolating numpy v1.24.3
    ✅ Bubble created: 1363 files

--- Creating scipy==1.12.0 bubble ---
🫧 Isolating scipy v1.12.0
    ✅ Bubble created: 3551 files

============================================================
  🚀 PHASE 3: Runtime Validation
============================================================

💥 NUMPY VERSION SWITCHING:

⚡ Activating numpy==1.24.3
 ✅ Version: 1.24.3
 🔢 Array sum: 6

⚡ Activating numpy==1.26.4
 ✅ Version: 1.26.4
 🔢 Array sum: 6

🔥 SCIPY EXTENSION VALIDATION:

🌋 Activating scipy==1.12.0
 ✅ Version: 1.12.0
 ♻️ Sparse matrix: 3 non-zeros

🌋 Activating scipy==1.16.1
 ✅ Version: 1.16.1
 ♻️ Sparse matrix: 3 non-zeros

🤯 COMBINATION TESTING:

🌀 Mix: numpy==1.24.3 + scipy==1.12.0
...
   🧪 Compatibility: [1. 2. 3.]

🌀 Mix: numpy==1.26.4 + scipy==1.16.1
...
   🧪 Compatibility: [1. 2. 3.]


 🚀 VALIDATION SUCCESSFUL! 🎇

============================================================
  🚀 PHASE 4: Environment Restoration
============================================================
   - Removing bubble: numpy-1.24.3
   - Removing bubble: numpy-1.26.4
   - Removing bubble: scipy-1.12.0

✅ Environment restored to initial state.

v1.0.0 Core Features

🛡️ Conflict Protection Engine
Real-time conflict detection and bubble initiation

🫧 Secure Bubble System
SHA-256 verified isolation with cross-bubble deduplication

🧠 Redis Knowledge Base
Cached metadata and dependency resolution

🔐 Integrity Verification
Security scanning and hash-based validation

🔀 Runtime Loader (Experimental)
Version switching in active scripts

🚀 Built-in Demonstrations
Try omnipkg demo and omnipkg validate

📊 Environment Analytics
Version tracking and health monitoring

Installation

pip install omnipkg
omnipkg demo  # See the system in action
omnipkg stress-test # See numpy/scipy version switching at runtime.

Licensing

Community Edition: GNU AGPLv3
Commercial License: Enterprise integration and proprietary use

Enterprise Features:

• Priority support and consulting
• Custom bubble strategies
• Compliance reporting
• On-premises deployment
• Team licensing

Contact: omnipkg@proton.me

---

The era of dependency compromises is over.
Stop wrestling environments. Start building solutions.

---

Ready to experience frictionless packaging?

pip install omnipkg
omnipkg demo  # See multiple ecosystems coexist