Bump GrantBirki/json-yaml-validate from 4.0.0 to 5.0.0

[dependabot]

Bumps GrantBirki/json-yaml-validate from 4.0.0 to 5.0.0.

Release notes

Sourced from GrantBirki/json-yaml-validate's releases.

v5.0.0

TL;DR

v5 is a major release for json-yaml-validate: the action now runs on node24, the internals have been rewritten in TypeScript, the runtime dependency surface is much smaller, path handling is stricter, and several new validation workflows are supported.

Most users can start by changing workflow references from GrantBirki/json-yaml-validate@v4 to GrantBirki/json-yaml-validate@v5, but please review the v4 to v5 migration guide before updating protected CI jobs.

Highlights

• Rewrote the action from JavaScript to TypeScript and moved the runtime to node24.
• Reduced runtime dependencies by replacing several packages with native implementations for action core behavior, PR comments, file discovery, coverage badge generation, and legacy YAML schema validation.
• Hardened validation path handling so explicit files, schemas, base directories, and schema mappings must resolve to regular files or directories inside the workspace.
• Allowed multi-document YAML by default, matching common Kubernetes-style YAML usage. Set allow_multiple_documents: "false" to preserve the old default.
• Added support for single-line, space-separated files input values.
• Added schema_mappings for validating different file groups against different JSON or YAML schemas in one action step.
• Added local-only inline schema discovery with use_inline_schema for JSON $schema references and YAML language-server schema comments when yaml_as_json is enabled.
• Added comment_on_success and update_comment so PR comments can be less noisy while still surfacing validation status.
• Strengthened tests, acceptance coverage, workflow hardening, package checks, and CI coverage thresholds.

Upgrade Notes

• Self-hosted runners must support JavaScript actions that run on node24.
• v5 intentionally rejects validation paths that escape the checked-out workspace or resolve through symlinks outside the workspace.
• File paths in logs and PR comments now prefer workspace-relative paths.
• JSON schema file skipping is now exact after realpath normalization, rather than substring-based.
• update_comment only updates matching validation comments authored by github-actions[bot].

See the full migration guide for examples and compatibility notes.

What's Changed

• Bump github/codeql-action from 3 to 4 in the github-actions group by @​dependabot[bot] in GrantBirki/json-yaml-validate#96
• Add agent guide by @​GrantBirki in GrantBirki/json-yaml-validate#118
• Harden unit test coverage by @​GrantBirki in GrantBirki/json-yaml-validate#119
• Harden acceptance coverage by @​GrantBirki in GrantBirki/json-yaml-validate#120
• Slim Node dependencies by @​GrantBirki in GrantBirki/json-yaml-validate#122
• Update Node dependencies by @​GrantBirki in GrantBirki/json-yaml-validate#123
• Migrate action to TypeScript by @​GrantBirki in GrantBirki/json-yaml-validate#124
• Consolidate agent guidance by @​GrantBirki in GrantBirki/json-yaml-validate#125
• Pin workflow action references by @​GrantBirki in GrantBirki/json-yaml-validate#126
• Support flat files input lists by @​GrantBirki in GrantBirki/json-yaml-validate#127
• Add success PR comments by @​GrantBirki in GrantBirki/json-yaml-validate#128
• Support updating PR comments by @​GrantBirki in GrantBirki/json-yaml-validate#129
• Fix YAML schema keyword field validation by @​GrantBirki in GrantBirki/json-yaml-validate#130
• Fix JSON meta-schema validation by @​GrantBirki in GrantBirki/json-yaml-validate#131
• Update AGENTS guidance from issue work by @​GrantBirki in GrantBirki/json-yaml-validate#132
• Support schema mappings by @​GrantBirki in GrantBirki/json-yaml-validate#133
• Support local inline schemas by @​GrantBirki in GrantBirki/json-yaml-validate#134
• Default to multi-document YAML validation by @​GrantBirki in GrantBirki/json-yaml-validate#135

... (truncated)

Commits

• 3ff7597 Merge pull request #143 from GrantBirki/strengthen-branch-coverage-tests
• 03dd72c Enforce branch and function coverage
• fcf4771 Strengthen branch coverage tests
• abb38be Merge pull request #142 from GrantBirki/update-doc-examples-v5
• 4a1c856 Update docs examples for v5
• 50d5a99 Merge pull request #140 from GrantBirki/schema-mapping-realpath-overlaps
• e20607e Merge branch 'main' into schema-mapping-realpath-overlaps
• 1a3d068 Merge pull request #141 from GrantBirki/v5-migration-guide
• 03c09a5 Add v5 migration guide
• c558c87 Normalize schema mapping overlap checks
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)