Skip to content

fix: use nested YAML metadata (not JSON string) for Codex compatibility #42

fix: use nested YAML metadata (not JSON string) for Codex compatibility

fix: use nested YAML metadata (not JSON string) for Codex compatibility #42

Triggered via push February 25, 2026 05:33
Status Success
Total duration 16s
Artifacts

ci.yml

on: push
skill-validation
12s
skill-validation
Fit to window
Zoom out
Zoom in

Annotations

1 warning
skill-validation
No file matched to [/home/runner/work/agent-deep-research/agent-deep-research/**/*requirements*.txt,/home/runner/work/agent-deep-research/agent-deep-research/**/*requirements*.in,/home/runner/work/agent-deep-research/agent-deep-research/**/*constraints*.txt,/home/runner/work/agent-deep-research/agent-deep-research/**/*constraints*.in,/home/runner/work/agent-deep-research/agent-deep-research/**/pyproject.toml,/home/runner/work/agent-deep-research/agent-deep-research/**/uv.lock,/home/runner/work/agent-deep-research/agent-deep-research/**/*.py.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.