fix: poetry_version format

[TOsmanov]

---

EntelligenceAI PR Summary

This PR enforces strict Poetry version pinning in the PyPI publishing workflow by adding an explicit equality operator.

• Changed poetry_version parameter from 2.1.1 to ==2.1.1 in .github/workflows/python-publish.yml
• Ensures exact version 2.1.1 is used, preventing implicit version resolution
• Improves CI/CD pipeline reliability and predictability

---

Confidence Score: 5/5 - Safe to Merge

• No review comments were generated, indicating the PR passed automated checks cleanly
• Heuristic analysis shows zero critical, significant, high-risk, medium, or low severity issues
• No existing unresolved comments that would block merging
• The PR appears to be safe to merge as-is based on all available indicators

[entelligence-ai-pr-reviews]

Walkthrough

This pull request updates the GitHub Actions workflow configuration for PyPI publishing to enforce stricter version control of Poetry. The change modifies the Poetry version specification from an implicit format to an explicit equality operator, ensuring that exactly version 2.1.1 is used during the publishing process. This prevents potential compatibility issues that could arise from implicit version resolution behavior in the poetry-publish action, providing more predictable and reliable CI/CD pipeline execution.

Changes

File(s)	Summary
.github/workflows/python-publish.yml	Updated Poetry version specification from 2.1.1 to ==2.1.1 in the poetry_version parameter to enforce exact version matching.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant GHA as GitHub Actions Workflow
    participant PPA as poetry-publish Action (v1.11)
    participant Poetry as Poetry Build Tool
    participant PyPI as PyPI Repository

    Note over GHA,PyPI: Build and Publish Pipeline

    GHA->>PPA: Trigger with configuration
    Note right of GHA: poetry_version: ==2.1.1<br/>(exact version pin)
    
    activate PPA
    PPA->>Poetry: Install Poetry version ==2.1.1
    activate Poetry
    Poetry-->>PPA: Poetry installed (exact version)
    deactivate Poetry
    
    PPA->>Poetry: Build package
    activate Poetry
    Poetry-->>PPA: Package artifacts ready
    deactivate Poetry
    
    PPA->>PyPI: Publish package
    Note right of PPA: Using PYPI_TOKEN
    activate PyPI
    PyPI-->>PPA: Publish successful
    deactivate PyPI
    
    PPA-->>GHA: Workflow complete
    deactivate PPA

Loading

---

🔗 Cross-Repository Impact Analysis

Enable automatic detection of breaking changes across your dependent repositories. → Set up now

Learn more about Cross-Repository Analysis

What It Does

• Automatically identifies repositories that depend on this code
• Analyzes potential breaking changes across your entire codebase
• Provides risk assessment before merging to prevent cross-repo issues

How to Enable

1. Visit Settings → Code Management
2. Configure repository dependencies
3. Future PRs will automatically include cross-repo impact analysis!

Benefits

• 🛡️ Prevent breaking changes across repositories
• 🔍 Catch integration issues before they reach production
• 📊 Better visibility into your multi-repo architecture

---