Gokul faf1af6ff5 fix(validators): reject non-mapping env values in validate (#90) ...

It turns out that `wrkflw validate` was happily accepting
`env: VAR=value` — a bare string — when GitHub Actions *only*
allows mappings for env. The reason is that the validate path
(evaluate_workflow_file) runs its own structural validators
but never actually checks the type of env fields. The JSON
schema gets it right, but it's only wired up in the parser
path, not the validator.

Add a validate_env() helper that checks env is either a YAML
mapping or an expression string (${{ }}), and wire it into
all three levels: top-level, job-level, and step-level. Tests
included for each.

Closes #89

2026-04-06 22:17:18 +05:30

..

actions.rs

feat(validate): cross-check local composite action required inputs (#78)

2026-04-02 13:49:47 +05:30

gitlab.rs

fix: resolve correctness, security, and parsing bugs across codebase (#73)

2026-04-01 23:06:48 +05:30

jobs.rs

fix(validators): reject non-mapping env values in validate (#90)

2026-04-06 22:17:18 +05:30

lib.rs

fix(validators): reject non-mapping env values in validate (#90)

2026-04-06 22:17:18 +05:30

matrix.rs

renamed

2025-08-09 17:03:03 +05:30

steps.rs

fix(validators): reject non-mapping env values in validate (#90)

2026-04-06 22:17:18 +05:30

triggers.rs

fix: resolve correctness, security, and parsing bugs across codebase (#73)

2026-04-01 23:06:48 +05:30