Update SchemaStore.org

[evanplaice]

Here's an interesting problem...

SchemaStore is like a CDN for JSON Schemas. It currently has a really outdated copy of the schema. What's the best approach to ensuring the copy of resume.json is kept up-to-date on the store?

Can this be automated via CD for major | minor releases only?

References:

• schemastore/schemastore - GitHub

[antialias]

SchemaStore kinda seems like a bad idea since they don't seem to version their schemas, but following the intent of this request, it looks like the only way to ensure that they have the latest version of jsonresume would be to submit a PR for a branch that has the latest version of the schema to be published to SchemaStore for resume.json.

Here are docs for how to use the github api to create a pull request.

[thomasdavis]

Great problem to identify, personally not sure of the solution.

[SethFalco]

What's the best approach to ensuring the copy of resume.json is kept up-to-date on the store?

We don't have to sync our changes with JSON Schema Store at all.

We're welcome to maintain our schema here, and just add a link to it to the catalog.json file. They're happy to accept links to external locations such as GitHub/GitLab repositories.

I'll make a PR now to point it to: https://raw.githubusercontent.com/jsonresume/resume-schema/v1.0.0/schema.json

SchemaStore kinda seems like a bad idea since they don't seem to version their schemas

That's not true, schemas can be versioned on JSON Schema Store.

[SethFalco]

Above has been merged, I only pointed it our 1.0.0 for now. We can add a latest version that points to master/main, or so if desirable.

If you're keen on every release being added automatically, then instead of updating the resume.json file, the PR should add a property to the versions array in the JSON Resume entry of catalog.json. (key == version, value == url to schema)