fix(schemas): move schema host to schemas.major.build, base URL to prod api - #139
Open
josegironn wants to merge 1 commit into
Open
fix(schemas): move schema host to schemas.major.build, base URL to prod api#139josegironn wants to merge 1 commit into
josegironn wants to merge 1 commit into
Conversation
…od api The published JSON Schemas moved from schemas.major.tech to schemas.major.build, and the sync/drift base URL default was a fictional api.major.tech. - schemas.go: compile IDs -> schemas.major.build (match vendored $id) - Makefile sync-schemas default + schemas-drift.yml base URL -> https://api.prod.major.build - re-vendored project/agent schema bytes ($id only) + SCHEMAS.sha256 - testdata $schema refs -> schemas.major.build Re-run `make sync-schemas` against prod once it serves GET /schemas/{project,agent}.json to confirm byte-for-byte; content already matches. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RXiDMg9GbDAqPFEXPYK1SH
josegironn
requested review from
exymax,
jasonzbao and
rishikesh-major
as code owners
July 24, 2026 06:18
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Two fixes tied to the published JSON Schemas moving to
schemas.major.build:$id/ host —schemas.major.tech→schemas.major.buildprojects/schemas.go: compile IDs (match the vendored$id)projects/schemas/{project,agent}.schema.json($idis the only content delta) +SCHEMAS.sha256projects/testdata/valid/**$schemarefsapi.major.tech; nowhttps://api.prod.major.build(Makefilesync-schemas+.github/workflows/schemas-drift.yml)Note
The vendored bytes were hand-updated (only the
$idstring differs from what the API serves). Oncemajor-technology/mono-builder#1903is deployed and prod servesGET /schemas/{project,agent}.json, re-runningmake sync-schemasshould be a content no-op (only refreshes thefetched:timestamp). The drift job still has its "not live yet" skip-with-warning branch — worth dropping per its own TODO once prod serves the endpoint.Related
major-technology/mono-builder#1903major-technology/project-template#1🤖 Generated with Claude Code
Made with Orca 🐋