aigency 0.0.1rc15474277__py3-none-any.whl → 0.0.1rc225507851__py3-none-any.whl

aigency-0.0.1rc225507851.dist-info/METADATA

@@ -0,0 +1,267 @@
+Metadata-Version: 2.4
+Name: aigency
+Version: 0.0.1rc225507851
+Summary: Add your description here
+Requires-Python: >=3.12
+Description-Content-Type: text/markdown
+Requires-Dist: google-adk>=1.11.0
+Requires-Dist: a2a-sdk==0.3.0
+Requires-Dist: litellm<1.73.0,>=1.72.6
+Requires-Dist: pyyaml==6.0.2
+Requires-Dist: PyJWT==2.10.1
+
+# aigency-lib
+
+A library for creating and managing AI agents.
+
+## Quick Start
+
+To test a simple agent:
+
+```bash
+cd examples/simple_agents/hello_world_agent
+docker compose up
+```
+
+## 🔧 Version Management
+
+This project includes an automated system for managing versions in both development and production.
+
+### Version Manager
+
+The `scripts/version_manager.py` script helps you manage your package versions locally.
+
+#### Available Commands
+
+##### 1. View current information
+```bash
+python scripts/version_manager.py show
+```
+**What it does:**
+- Shows the current version in `pyproject.toml`
+- Shows the current git branch
+- Shows the current commit
+- If you're not on `main`, suggests a development version
+
+**Example output:**
+```
+Current version: 0.0.1
+Branch: feature/new-agent
+Commit: a1b2c3d
+Suggested dev version: 0.0.1.dev20250409143022+feature/new-agent.a1b2c3d
+```
+
+##### 2. Create development version
+```bash
+python scripts/version_manager.py dev
+```
+**What it does:**
+- Takes the current version and creates a development version
+- Format: `version.devYYYYMMDDHHMMSS+branch.commit`
+- Automatically updates the `pyproject.toml`
+
+**Example:**
+```bash
+# If you're on branch "feature/auth" with commit "abc123"
+python scripts/version_manager.py dev
+# Result: 0.0.1.dev20250409143022
+```
+
+##### 3. Set specific version
+```bash
+python scripts/version_manager.py set --version "0.1.0"
+```
+**What it does:**
+- Changes the version to the one you specify
+- Useful for releases or to fix versions
+
+**Examples:**
+```bash
+# Release version
+python scripts/version_manager.py set --version "1.0.0"
+
+# Beta version
+python scripts/version_manager.py set --version "1.0.0b1"
+
+# Alpha version
+python scripts/version_manager.py set --version "1.0.0a1"
+```
+
+##### 4. Create Release Candidate version
+```bash
+python scripts/version_manager.py rc --version "1.0.1"
+```
+**What it does:**
+- Creates an RC version with the format `version-rc<commit>`
+- Useful for preparing releases on `release/*` branches
+
+##### 5. Validate current version
+```bash
+python scripts/version_manager.py validate
+```
+**What it does:**
+- Validates that the current version is appropriate for the branch
+- Verifies semantic format on `main` and `release/*` branches
+
+##### 6. Create dev with custom base version
+```bash
+python scripts/version_manager.py dev --base-version "0.2.0"
+```
+**What it does:**
+- Uses a different base version than the current one
+- Useful when you want to prepare a dev version for the next release
+
+### 🚀 Recommended Workflow
+
+#### For daily development:
+```bash
+# 1. View current status
+python scripts/version_manager.py show
+
+# 2. If you're on a feature branch, create dev version
+python scripts/version_manager.py dev
+
+# 3. Make your changes and commits
+git add .
+git commit -m "feat: new functionality"
+
+# 4. If you need to update the dev version (optional)
+python scripts/version_manager.py dev
+```
+
+#### For releases:
+```bash
+# 1. On main branch, set release version
+python scripts/version_manager.py set --version "1.0.0"
+
+# 2. Commit the version
+git add pyproject.toml
+git commit -m "bump: version 1.0.0"
+
+# 3. Use GitHub workflow to publish
+```
+
+#### For testing:
+```bash
+# Create specific test version
+python scripts/version_manager.py set --version "1.0.0rc1"
+```
+
+### ⚠️ PyPI Limitations
+
+PyPI doesn't allow "local versions" (versions with `+` and local identifiers). That's why we've adapted the format:
+
+- ❌ Not allowed: `1.0.0.dev20250409+feature.abc123`
+- ✅ Allowed: `1.0.0.dev20250409`
+
+**Solution for Release Candidates:**
+- We convert the commit hash (hexadecimal) to decimal
+- Example: commit `abc123` → `11256099` → version `1.0.1rc11256099`
+- This maintains commit uniqueness in a PyPI-compatible format
+
+**Result:**
+- Dev versions include unique timestamp
+- RC versions include commit hash (in decimal)
+- We maintain traceability without using local versions
+
+### 📋 Practical Use Cases
+
+**Scenario 1: Working on a feature**
+```bash
+git checkout -b feature/new-auth
+python scripts/version_manager.py dev
+# Now you have: 0.0.1.dev20250409143022
+```
+
+**Scenario 2: Preparing release**
+```bash
+git checkout main
+python scripts/version_manager.py set --version "1.0.0"
+git add pyproject.toml
+git commit -m "release: v1.0.0"
+```
+
+**Scenario 3: Preparing Release Candidate**
+```bash
+git checkout -b release/1.0.1
+python scripts/version_manager.py rc --version "1.0.1"
+# Result: 1.0.1rc12345678 (where 12345678 is the commit hash in decimal)
+```
+
+**Scenario 4: Urgent hotfix**
+```bash
+git checkout -b hotfix/critical-bug
+python scripts/version_manager.py dev --base-version "1.0.1"
+# Result: 1.0.1.dev20250409143022
+```
+
+## 🔄 Intelligent CI/CD Workflow
+
+The project includes a single intelligent workflow (`python-publish.yml`) that automatically handles different version types based on the branch:
+
+### Automatic behavior by branch:
+
+#### 🚀 `main` Branch - Production Versions
+- **Trigger**: Push to `main` or manual execution
+- **Version**: Uses exactly the version from `pyproject.toml`
+- **Validations**:
+  - ✅ Verifies it's a valid semantic version (e.g.: `1.0.0`)
+  - ✅ Verifies it doesn't already exist on PyPI
+  - ❌ Fails if it contains development suffixes (`dev`, `rc`, `alpha`, `beta`)
+- **Target**: PyPI production
+
+#### 🎯 `release/*` Branches - Release Candidates
+- **Trigger**: Push to `release/X.Y.Z` branch or manual execution
+- **Version**: `X.Y.ZrcN` where N is the commit hash in decimal (e.g.: `1.0.1rc12345678`)
+- **Validations**:
+  - ✅ Verifies that `X.Y.Z` is a valid semantic version
+  - ✅ Extracts version from branch name
+  - ✅ Uses commit hash as unique identifier
+  - ✅ PyPI-compatible format
+- **Target**: PyPI production
+- **Example**: Branch `release/1.0.1` + commit `abc123` → Version `1.0.1rc11256099`
+
+#### 🔧 Other Branches - Development Versions
+- **Trigger**: Push to any other branch or manual execution
+- **Version**: `current.devYYYYMMDDHHMMSS` (e.g.: `0.0.1.dev20250409143022`)
+- **Target**: PyPI production
+- **Note**: No local versions for PyPI compatibility
+
+### Recommended workflow:
+
+```bash
+# 1. Development on feature branch
+git checkout -b feature/new-functionality
+# Automatic version: 0.0.1.dev20250409143022+feature-new-functionality.abc123
+
+# 2. Prepare release
+git checkout -b release/1.0.0
+git push origin release/1.0.0
+# Automatic version: 1.0.0rc12345678
+
+# 3. Final release
+git checkout main
+python scripts/version_manager.py set --version "1.0.0"
+git add pyproject.toml
+git commit -m "release: v1.0.0"
+git push origin main
+# Version: 1.0.0 (with validations)
+```
+
+## 📦 Installation
+
+```bash
+pip install aigency
+```
+
+## 🛠️ Development
+
+1. Clone the repository
+2. Install development dependencies
+3. Use the version manager to manage versions during development
+
+```bash
+git clone <repo-url>
+cd aigency-lib
+pip install -e .
+```

{aigency-0.0.1rc15474277.dist-info → aigency-0.0.1rc225507851.dist-info}/RECORD

@@ -9,7 +9,7 @@ aigency/utils/config_service.py,sha256=ql2NsQBjhwH6phbsbqp698je1NmAUlZuyXOE0Bb9L
 aigency/utils/logger.py,sha256=NYvEknt2BeSqn484ivaLFwP0KbAtBxDXFoJiiKiXKeI,3796
 aigency/utils/singleton.py,sha256=u5stRwgwiXRt6b2vTX4W8zuchWvQ9kbcvztQDceaF3E,313
 aigency/utils/utils.py,sha256=1eA-RxMZW6QIxhrK9TbxysxwKhGiJqjrvOk69xR-zKo,2698
-aigency-0.0.1rc15474277.dist-info/METADATA,sha256=zflUAom3vGz7ScCKBi9zFHW3GagZkUhwREX-T8iqXt8,7397
-aigency-0.0.1rc15474277.dist-info/WHEEL,sha256=_zCd3N1l69ArxyTb8rzEoP9TpbYXkqRFSNOD5OuxnTs,91
-aigency-0.0.1rc15474277.dist-info/top_level.txt,sha256=nr33Htucgjs3wJFNugPV8w7b9ZgSnytxCtRiinR3eb8,8
-aigency-0.0.1rc15474277.dist-info/RECORD,,
+aigency-0.0.1rc225507851.dist-info/METADATA,sha256=ZG4oKDTI1SDA02JiBQzizH0PCMr7Df9OjjxnSTM2WJI,7170
+aigency-0.0.1rc225507851.dist-info/WHEEL,sha256=_zCd3N1l69ArxyTb8rzEoP9TpbYXkqRFSNOD5OuxnTs,91
+aigency-0.0.1rc225507851.dist-info/top_level.txt,sha256=nr33Htucgjs3wJFNugPV8w7b9ZgSnytxCtRiinR3eb8,8
+aigency-0.0.1rc225507851.dist-info/RECORD,,

aigency-0.0.1rc15474277.dist-info/METADATA

@@ -1,267 +0,0 @@
-Metadata-Version: 2.4
-Name: aigency
-Version: 0.0.1rc15474277
-Summary: Add your description here
-Requires-Python: >=3.12
-Description-Content-Type: text/markdown
-Requires-Dist: google-adk>=1.11.0
-Requires-Dist: a2a-sdk==0.3.0
-Requires-Dist: litellm<1.73.0,>=1.72.6
-Requires-Dist: pyyaml==6.0.2
-Requires-Dist: PyJWT==2.10.1
-
-# aigency-lib
-
-Una librería para crear y gestionar agentes de IA.
-
-## Inicio rápido
-
-Para probar un agente simple:
-
-```bash
-cd examples/simple_agents/hello_world_agent
-docker compose up
-```
-
-## 🔧 Gestión de versiones
-
-Este proyecto incluye un sistema automatizado para gestionar versiones tanto en desarrollo como en producción.
-
-### Version Manager
-
-El script `scripts/version_manager.py` te ayuda a gestionar las versiones de tu paquete de forma local.
-
-#### Comandos disponibles
-
-##### 1. Ver información actual
-```bash
-python scripts/version_manager.py show
-```
-**Qué hace:**
-- Muestra la versión actual en `pyproject.toml`
-- Muestra la rama git actual
-- Muestra el commit actual
-- Si no estás en `main`, sugiere una versión de desarrollo
-
-**Ejemplo de salida:**
-```
-Versión actual: 0.0.1
-Rama: feature/new-agent
-Commit: a1b2c3d
-Versión dev sugerida: 0.0.1.dev20250409143022+feature/new-agent.a1b2c3d
-```
-
-##### 2. Crear versión de desarrollo
-```bash
-python scripts/version_manager.py dev
-```
-**Qué hace:**
-- Toma la versión actual y crea una versión de desarrollo
-- Formato: `version.devYYYYMMDDHHMMSS+branch.commit`
-- Actualiza automáticamente el `pyproject.toml`
-
-**Ejemplo:**
-```bash
-# Si estás en rama "feature/auth" con commit "abc123"
-python scripts/version_manager.py dev
-# Resultado: 0.0.1.dev20250409143022
-```
-
-##### 3. Establecer versión específica
-```bash
-python scripts/version_manager.py set --version "0.1.0"
-```
-**Qué hace:**
-- Cambia la versión a la que especifiques
-- Útil para releases o para corregir versiones
-
-**Ejemplos:**
-```bash
-# Versión de release
-python scripts/version_manager.py set --version "1.0.0"
-
-# Versión beta
-python scripts/version_manager.py set --version "1.0.0b1"
-
-# Versión alpha
-python scripts/version_manager.py set --version "1.0.0a1"
-```
-
-##### 4. Crear versión Release Candidate
-```bash
-python scripts/version_manager.py rc --version "1.0.1"
-```
-**Qué hace:**
-- Crea una versión RC con el formato `version-rc<commit>`
-- Útil para preparar releases en ramas `release/*`
-
-##### 5. Validar versión actual
-```bash
-python scripts/version_manager.py validate
-```
-**Qué hace:**
-- Valida que la versión actual sea apropiada para la rama
-- Verifica formato semántico en `main` y ramas `release/*`
-
-##### 6. Crear dev con versión base personalizada
-```bash
-python scripts/version_manager.py dev --base-version "0.2.0"
-```
-**Qué hace:**
-- Usa una versión base diferente a la actual
-- Útil cuando quieres preparar una dev version para la próxima release
-
-### 🚀 Flujo de trabajo recomendado
-
-#### Para desarrollo diario:
-```bash
-# 1. Ver estado actual
-python scripts/version_manager.py show
-
-# 2. Si estás en una rama feature, crear versión dev
-python scripts/version_manager.py dev
-
-# 3. Hacer tus cambios y commits
-git add .
-git commit -m "feat: nueva funcionalidad"
-
-# 4. Si necesitas actualizar la versión dev (opcional)
-python scripts/version_manager.py dev
-```
-
-#### Para releases:
-```bash
-# 1. En rama main, establecer versión de release
-python scripts/version_manager.py set --version "1.0.0"
-
-# 2. Commit de la versión
-git add pyproject.toml
-git commit -m "bump: version 1.0.0"
-
-# 3. Usar el workflow de GitHub para publicar
-```
-
-#### Para testing:
-```bash
-# Crear versión de test específica
-python scripts/version_manager.py set --version "1.0.0rc1"
-```
-
-### ⚠️ Limitaciones de PyPI
-
-PyPI no permite "local versions" (versiones con `+` y identificadores locales). Por eso, hemos adaptado el formato:
-
-- ❌ No permitido: `1.0.0.dev20250409+feature.abc123`
-- ✅ Permitido: `1.0.0.dev20250409`
-
-**Solución para Release Candidates:**
-- Convertimos el hash del commit (hexadecimal) a decimal
-- Ejemplo: commit `abc123` → `11256099` → versión `1.0.1rc11256099`
-- Esto mantiene la unicidad del commit en un formato compatible con PyPI
-
-**Resultado:**
-- Las versiones dev incluyen timestamp único
-- Las versiones RC incluyen el hash del commit (en decimal)
-- Mantenemos trazabilidad sin usar local versions
-
-### 📋 Casos de uso prácticos
-
-**Escenario 1: Trabajando en una feature**
-```bash
-git checkout -b feature/new-auth
-python scripts/version_manager.py dev
-# Ahora tienes: 0.0.1.dev20250409143022
-```
-
-**Escenario 2: Preparando release**
-```bash
-git checkout main
-python scripts/version_manager.py set --version "1.0.0"
-git add pyproject.toml
-git commit -m "release: v1.0.0"
-```
-
-**Escenario 3: Preparando Release Candidate**
-```bash
-git checkout -b release/1.0.1
-python scripts/version_manager.py rc --version "1.0.1"
-# Resultado: 1.0.1rc12345678 (donde 12345678 es el hash del commit en decimal)
-```
-
-**Escenario 4: Hotfix urgente**
-```bash
-git checkout -b hotfix/critical-bug
-python scripts/version_manager.py dev --base-version "1.0.1"
-# Resultado: 1.0.1.dev20250409143022
-```
-
-## 🔄 Workflow de CI/CD Inteligente
-
-El proyecto incluye un único workflow inteligente (`python-publish.yml`) que maneja automáticamente diferentes tipos de versiones según la rama:
-
-### Comportamiento automático por rama:
-
-#### 🚀 Rama `main` - Versiones de Producción
-- **Trigger**: Push a `main` o ejecución manual
-- **Versión**: Usa exactamente la versión del `pyproject.toml`
-- **Validaciones**:
-  - ✅ Verifica que sea una versión semántica válida (ej: `1.0.0`)
-  - ✅ Verifica que no exista ya en PyPI
-  - ❌ Falla si contiene sufijos de desarrollo (`dev`, `rc`, `alpha`, `beta`)
-- **Destino**: PyPI producción
-
-#### 🎯 Ramas `release/*` - Release Candidates
-- **Trigger**: Push a rama `release/X.Y.Z` o ejecución manual
-- **Versión**: `X.Y.ZrcN` donde N es el hash del commit en decimal (ej: `1.0.1rc12345678`)
-- **Validaciones**:
-  - ✅ Verifica que `X.Y.Z` sea una versión semántica válida
-  - ✅ Extrae la versión del nombre de la rama
-  - ✅ Usa hash del commit como identificador único
-  - ✅ Formato compatible con PyPI
-- **Destino**: PyPI producción
-- **Ejemplo**: Rama `release/1.0.1` + commit `abc123` → Versión `1.0.1rc11256099`
-
-#### 🔧 Otras ramas - Versiones de Desarrollo
-- **Trigger**: Push a cualquier otra rama o ejecución manual
-- **Versión**: `current.devYYYYMMDDHHMMSS` (ej: `0.0.1.dev20250409143022`)
-- **Destino**: PyPI producción
-- **Nota**: Sin local versions para compatibilidad con PyPI
-
-### Flujo de trabajo recomendado:
-
-```bash
-# 1. Desarrollo en feature branch
-git checkout -b feature/new-functionality
-# Versión automática: 0.0.1.dev20250409143022+feature-new-functionality.abc123
-
-# 2. Preparar release
-git checkout -b release/1.0.0
-git push origin release/1.0.0
-# Versión automática: 1.0.0rc12345678
-
-# 3. Release final
-git checkout main
-python scripts/version_manager.py set --version "1.0.0"
-git add pyproject.toml
-git commit -m "release: v1.0.0"
-git push origin main
-# Versión: 1.0.0 (con validaciones)
-```
-
-## 📦 Instalación
-
-```bash
-pip install aigency
-```
-
-## 🛠️ Desarrollo
-
-1. Clona el repositorio
-2. Instala las dependencias de desarrollo
-3. Usa el version manager para gestionar versiones durante el desarrollo
-
-```bash
-git clone <repo-url>
-cd aigency-lib
-pip install -e .
-```