Skip to content

feat(rumdl): host schema locally for direct URL access#5305

Merged
hyperupcall merged 1 commit into
SchemaStore:masterfrom
rvben:add-rumdl-schema-file
Jan 23, 2026
Merged

feat(rumdl): host schema locally for direct URL access#5305
hyperupcall merged 1 commit into
SchemaStore:masterfrom
rvben:add-rumdl-schema-file

Conversation

@rvben

@rvben rvben commented Jan 22, 2026

Copy link
Copy Markdown
Contributor

Hosts the rumdl JSON schema locally to enable direct URL access at https://json.schemastore.org/rumdl.json

The previous PR (#5052) added rumdl to the catalog with an external URL pointing to GitHub. This worked for catalog-based tooling, but the direct SchemaStore URL returned 404. Hosting the schema locally enables:

  • $schema references in config files
  • Validators that don't consult the catalog
  • CDN-backed reliable access

Changes:

  • Add src/schemas/json/rumdl.json
  • Update catalog entry URL from external GitHub raw URL to local schema

Related Links:

@github-actions

Copy link
Copy Markdown
Contributor

Thanks for the PR!

This section of the codebase is owned by @madskristensen and @hyperupcall - if they write a comment saying "LGTM" then it will be merged.

@rvben rvben force-pushed the add-rumdl-schema-file branch 4 times, most recently from 3d5b2be to 48ff57f Compare January 22, 2026 21:05
Adds the rumdl schema file to the repository so it can be accessed
directly at https://json.schemastore.org/rumdl.json

Previously, the catalog entry pointed to an external GitHub raw URL,
which meant the direct SchemaStore URL returned 404. This change
enables users to use $schema references and validators that don't
consult the catalog.

Changes:
- Add src/schemas/json/rumdl.json
- Update catalog.json URL to use local schema
@rvben rvben force-pushed the add-rumdl-schema-file branch from 48ff57f to 0c988ea Compare January 22, 2026 21:08
@hyperupcall

Copy link
Copy Markdown
Member

Thanks!

@hyperupcall hyperupcall merged commit 38c1489 into SchemaStore:master Jan 23, 2026
5 checks passed
@j178 j178 mentioned this pull request Feb 4, 2026
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.

2 participants