fix yaml_include in full image

[TOsmanov]

---

EntelligenceAI PR Summary

This PR adds foliantcontrib.yaml_include >= 1.0.1 to the force-reinstall Python dependencies list.

• Added foliantcontrib.yaml_include >= 1.0.1 to dependency_files/python_packages/requirements_force_reinstall.txt
• Ensures the package is reinstalled alongside existing dependencies foliantcontrib.includes and foliantcontrib.utils

---

Confidence Score: 5/5 - Safe to Merge

• No review comments were generated, indicating the PR appears clean
• Zero critical, significant, or medium issues identified by automated analysis
• No existing unresolved comments that could block the merge
• Coverage gap exists (0/2 files reviewed), but heuristic ceiling allows score of 5

[entelligence-ai-pr-reviews]

Walkthrough

This update adds foliantcontrib.yaml_include >= 1.0.1 as a new dependency to the force-reinstall requirements file. This ensures the package is included during forced reinstallation processes alongside the existing foliantcontrib.includes and foliantcontrib.utils dependencies.

Changes

File(s)	Summary
dependency_files/python_packages/requirements_force_reinstall.txt	Added foliantcontrib.yaml_include >= 1.0.1 as a new dependency entry for forced reinstallation.

Sequence Diagram

This diagram shows the interactions between components:

sequenceDiagram
    participant CI as CI/CD Pipeline
    participant PIP as pip installer
    participant Includes as foliantcontrib.includes
    participant Utils as foliantcontrib.utils
    participant YAMLInclude as foliantcontrib.yaml_include
    participant Foliant as Foliant Build

    Note over CI,YAMLInclude: Dependency installation phase (requirements_force_reinstall.txt)

    CI->>PIP: install --force-reinstall requirements
    activate PIP

    PIP->>Includes: install foliantcontrib.includes >= 1.1.21
    Includes-->>PIP: installed ✓

    PIP->>Utils: install foliantcontrib.utils >= 1.0.8
    Utils-->>PIP: installed ✓

    PIP->>YAMLInclude: install foliantcontrib.yaml_include >= 1.0.1 (NEW)
    YAMLInclude-->>PIP: installed ✓

    deactivate PIP
    PIP-->>CI: all dependencies ready

    Note over CI,Foliant: Documentation build phase

    CI->>Foliant: trigger doc build
    activate Foliant

    Foliant->>Includes: process file includes
    Includes->>Utils: shared utilities
    Utils-->>Includes: utilities provided
    Includes-->>Foliant: includes resolved

    Foliant->>YAMLInclude: process YAML include directives (NEW)
    YAMLInclude-->>Foliant: YAML content resolved

    Foliant-->>CI: build complete
    deactivate Foliant

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

---