Package Version Pinning System

[mikejmorgan-ai]

Description

Pin specific package versions to prevent unwanted updates.

Requirements

• Version pinning configuration
• Pin files management
• Prevent accidental updates
• Override mechanism
• Pin validation
• Export/import pin configurations

Acceptance Criteria

• Pin specific versions
• Prevent updates to pinned packages
• Override with flags
• Pin configuration files
• Import/export pins
• Validation and warnings
• Unit tests included (>80% coverage)
• Documentation with pinning strategies

Example Usage

$ cortex pin add postgresql@14.10
✓  Pinned postgresql to version 14.10

$ cortex update
Updating packages...
   ⊘ postgresql (pinned to 14.10)
   ✓  nginx 1.24.0 → 1.25.0
   
$ cortex pin list
postgresql: 14.10 (pinned 5 days ago)
python: 3.11.* (pinned to minor version)

$ cortex update postgresql --force
⚠️  Package is pinned. Override? [y/N]:

Skills: Python, version management, package constraints
Bounty: $25 upon merge
Priority: Medium

[mikejmorgan-ai]

🎯 Closing for MVP Focus

This issue is being closed to help the team focus on MVP-critical features (#1-45).

This is NOT abandoned - it's an important feature we'll revisit after MVP completion.

Timeline:

• Now (Nov-Dec 2024): Focus on MVP (Issues Build LLM integration layer for command interpretation cortex#1-45)
• January 2025: Reopen post-MVP features
• February 2025: Seed funding round

Want to work on this anyway?
Comment below and we can discuss! We're always open to great contributions.

Tracking: Labeled as post-mvp for easy filtering when we reopen.

Thanks for understanding! 🚀

— Mike (@mikejmorgan-ai)

[divanshu-go]

Can I get this issue assigned ?

[DipeshDalmia]

Can I get this issue assigned @mikejmorgan-ai ?