From 7787d02e3a58da5967ecefbbab7bb73e3c826ec1 Mon Sep 17 00:00:00 2001 From: chaksaray Date: Sun, 9 Aug 2026 23:33:55 +0700 Subject: [PATCH] fix: ave-record-1.0.0.schema.json's $id still pointed at ave.bawbel.io Every other schema file's $id already reads aveproject.org (the org-move checklist's section 5.1 covered ave-record-1.1.0 and the others); this frozen v1.0.0 snapshot was missed. Flagged by ave-site's scripts/publish-schemas.js, which warns about it at every build without altering it -- publishing a copy of a wrong $id isn't this repo's problem to paper over. Also doubles as the end-to-end trigger for this session's real fix: aveproject/ave-site's Pages source was set to "Deploy from a branch" (legacy, zero-build static serving) racing against the actual deploy.yml Actions pipeline -- the legacy path was winning, silently re-serving whatever records.js happened to be committed to git regardless of what deploy.yml had just correctly rebuilt. Switched that repo's Pages source to "GitHub Actions" via the API; this PR, once merged, is the real verification that notify-ave-site.yml (push to schema/**) -> repository_dispatch -> ave-site's deploy.yml -> GitHub Pages actually lands live now, not just that each piece works in isolation. --- schema/ave-record-1.0.0.schema.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/schema/ave-record-1.0.0.schema.json b/schema/ave-record-1.0.0.schema.json index d45e387..b9e3469 100644 --- a/schema/ave-record-1.0.0.schema.json +++ b/schema/ave-record-1.0.0.schema.json @@ -1,6 +1,6 @@ { "$schema": "https://json-schema.org/draft/2020-12/schema", - "$id": "https://ave.bawbel.io/schema/ave-record-1.0.0.schema.json", + "$id": "https://aveproject.org/schema/ave-record-1.0.0.schema.json", "title": "AVE Record", "description": "AVE (the behavioral vulnerability enumeration standard for agentic AI components) \u2014 static definition of one behavioral vulnerability class. Schema v1.0.0.", "type": "object",