[docs] docs: add awf-config.v1.schema.json references to config spec#2393
[docs] docs: add awf-config.v1.schema.json references to config spec#2393github-actions[bot] wants to merge 1 commit intomainfrom
Conversation
The feat #2384 introduced a versioned awf-config.v1.schema.json schema file alongside the existing awf-config.schema.json. Update the AWF Configuration Specification to document both files and add a stable pinning reference table consistent with docs/releasing.md. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This comment has been minimized.
This comment has been minimized.
🔥 Smoke Test: Copilot BYOK (Offline) Mode
Running in BYOK offline mode ( PR author: Overall: PARTIAL PASS (2 tests indeterminate due to unexpanded template vars in workflow)
|
|
Smoke Test Results ✅ GitHub MCP: PR #2396, PR #2384 Status: PASS
|
🏗️ Build Test Suite Results
Overall: 0/8 ecosystems passed — ❌ FAIL Error DetailsAll repository clones failed. The Error: This affected all 8 ecosystems: Bun, C++, Deno, .NET, Go, Java, Node.js, Rust.
|
🔥 Smoke Test Results
Overall: PASS PR by
|
|
PRs: Warning Firewall blocked 1 domainThe following domain was blocked by the firewall during workflow execution:
network:
allowed:
- defaults
- "registry.npmjs.org"See Network Configuration for more information.
|
Smoke Test: GitHub Actions Services Connectivity
Overall: FAIL —
|
Smoke Test Results: Gemini Engine Validation
Overall Status: PASS CC:
|
Documentation Sync - May 2026
This PR synchronizes
docs/awf-config-spec.mdwith code changes from the past 7 days.Changes Made
docs/awf-config-spec.md: Added documentation for the versionedawf-config.v1.schema.jsonschema file and a stable-URL pinning reference table, consistent with the information already present indocs/releasing.md.Code Changes Referenced
08cd698:feat: validate config files against published JSON Schema at runtime (#2384)— introduceddocs/awf-config.v1.schema.jsonas a stable versioned copy of the config schema, alongside the existingdocs/awf-config.schema.json. The spec only referenced the unversioned file; external consumers should pin to the versioned URL.Verification
docs/releasing.mdstyle