Update catalog.json

[BlackwallDaemon]

Fix Versions for Semgrep

[github-actions]

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.

[hyperupcall]

Thanks - shouldn't all the versions continue to exist? They still work for me

[BlackwallDaemon]

@hyperupcall They should - it's all a matter of the version in the url, But it's always the latest one so no need for them.

[hyperupcall]

@BlackwallDaemon Does semgrep.json currently fail to resolve/redirect to the schema? I worry that with this change, the "canonical" URL will be written in two different places and has the potential to go out of sync

[BlackwallDaemon]

@BlackwallDaemon Does semgrep.json currently fail to resolve/redirect to the schema? I worry that with this change, the "canonical" URL will be written in two different places and has the potential to go out of sync

Currently the semgrep.json always will be the latest one so long it's from their repo. What do you mean by out of sync?

[hyperupcall]

By out of sync, I mean that this value and this value (from your proposed change) will have the potential to be different. That is, an IDE finding the correct schema for a semgrep.json file, and a user quering the website for json.schemastore.com/json/schema.json will potentially return schemas with different structures). That's why the ref "$ref" exists - it keeps a single source of truth while preserving compatibility.

So what I mean, is that semgrep.json should not be changed because it can potentially "be out of sync", unless there is a more important issue at play

[hyperupcall]

So unless I'm mistaken by anything, I'll be closing this issue

[BlackwallDaemon]

So unless I'm mistaken by anything, I'll be closing this issue

You can merge them - they are the same schema basically