Skip to content

fix: ave-record-1.0.0.schema.json's $id still pointed at ave.bawbel.io - #166

Merged
chaksaray merged 1 commit into
developfrom
fix/stale-schema-id-bawbel-io-develop
Aug 9, 2026
Merged

chaksaray merged 1 commit into
developfrom
fix/stale-schema-id-bawbel-io-develop

Conversation

@chaksaray

Copy link
Copy Markdown
Contributor

Same fix as #165, which already merged to `main`. Opening this against `develop` too since the two branches are otherwise in sync right now and this repo's history pairs a `main` PR with a matching `develop` PR.

Every other schema file's `$id` already reads `aveproject.org` (org-move checklist §5.1); 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.

Leaving this for manual merge, not merging it myself.

🤖 Generated with Claude Code

Same fix as #165 (merged to main), opened here against develop since
main and develop are otherwise in sync and this repo's convention
pairs a main PR with a develop PR. Every other schema file's $id
already reads aveproject.org (org-move checklist section 5.1); 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.
@chaksaray
chaksaray merged commit 47d628f into develop Aug 9, 2026
6 checks passed
@chaksaray
chaksaray deleted the fix/stale-schema-id-bawbel-io-develop branch August 9, 2026 16:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant