HAL9000
e6094d1fb7
- Fix step definitions: remove unused imports (sys, Any, Dict), move all imports to module level, drop noqa suppressor, fix docstring step to use context.text, use packaging.version for correct semver check - Upgrade version floor from 6.0.2 to 6.0.3 in step text and feature file to match pyproject.toml constraint and issue requirement - Fix CONTRIBUTORS.md: correct PR number (#11012 -> #11017), issue reference (#13605 -> #11012), and version string (6.0.2 -> 6.0.3) ISSUES CLOSED: #11012
19 lines
829 B
Gherkin
19 lines
829 B
Gherkin
Feature: PyYAML runtime dependency is explicitly declared
|
|
As a developer ensuring supply-chain security
|
|
I want PyYAML declared as an explicit runtime dependency in pyproject.toml
|
|
So that the YAML actor config loader is never silently broken by transitive dep changes
|
|
|
|
Scenario: PyYAML is available at runtime for actor config loading
|
|
When I verify that PyYAML can be imported
|
|
Then PyYAML should be importable without error
|
|
And its version should be >= 6.0.3 to mitigate CVE-2025-8045
|
|
|
|
Scenario: Actor YAML loading works with available PyYAML
|
|
Given a valid YAML actor config file "test.yaml" with content:
|
|
"""
|
|
provider: openai
|
|
model: gpt-4
|
|
"""
|
|
When I load the YAML config using PyYAML safe_load
|
|
Then the loaded config should equal {"provider": "openai", "model": "gpt-4"}
|