Current Behavior
Contributor docs can become stale when dependency versions change in package.json.
For example, setup/troubleshooting sections may continue to reference old React/Gatsby versions, which causes confusion for newcomers and extra maintainer support.
Desired Situation
Add an automated guardrail that validates key version references in contributor-facing docs (starting with CONTRIBUTING.md) against current values in package.json.
Expected outcome:
- CI fails when documented versions are outdated.
- CI passes when docs and dependencies are aligned.
- Failure message clearly indicates what file/value should be updated.
Contributor Resources and Handbook
The layer5.io website uses Gatsby, React, and GitHub Pages. Site content is found under the master branch.
Join the Layer5 Community by submitting your community member form.
Current Behavior
Contributor docs can become stale when dependency versions change in
package.json.For example, setup/troubleshooting sections may continue to reference old React/Gatsby versions, which causes confusion for newcomers and extra maintainer support.
Desired Situation
Add an automated guardrail that validates key version references in contributor-facing docs (starting with
CONTRIBUTING.md) against current values inpackage.json.Expected outcome:
Contributor Resources and Handbook
The layer5.io website uses Gatsby, React, and GitHub Pages. Site content is found under the
masterbranch.