Multiple broken schema URLs in the catalog

Area with issue?

JSON Schema

✔️ Expected Behavior

Apparently we have more than one schema with broken URLs:

Failed to cache https://raw.githubusercontent.com/dolittle/DotNET.Fundamentals/master/Schemas/Tenancy.Configuration/tenant-map.json
Failed to cache https://raw.githubusercontent.com/dolittle/DotNET.SDK/master/Schemas/Applications.Configuration/topology.json
Failed to cache https://www.facets.cloud/assets/fsdl/application.schema.json
Failed to cache https://raw.githubusercontent.com/fossas/fossa-cli/master/docs/references/files/fossa-deps.schema.json
Failed to cache https://hazelcast.com/schema/config/hazelcast-config-5.1.json
Failed to cache https://raw.githubusercontent.com/blackbaud/skyux-config/master/skyuxconfig-schema.json
Failed to cache https://raw.githubusercontent.com/DotNetAnalyzers/StyleCopAnalyzers/master/StyleCop.Analyzers/StyleCop.Analyzers/Settings/stylecop.schema.json
Failed to cache https://raw.githubusercontent.com/dotnet/Nerdbank.GitVersioning/master/src/NerdBank.GitVersioning/version.schema.json
Failed to cache https://webcomponents.dev/assets2/schemas/studio.config.json

❌ Actual Behavior

We should not have broken URL on our catalog. While I suppose that downtimes are possible, I doubt that these are only temporary hiccups.

Probably we need scheduled pipeline to check URLs for being valid and maybe even checking that the schemas are passing validation too.

I am not sure what we should do about this, first we would need to ensure we record contacts for each externally hosted schema, so we would know whom to contact.

Removing broken entries is easy, but often that is not a fix.

YAML or JSON file that does not work.

No response

IDE or code editor.

Visual Studio Code

Are you making a PR for this?

No, someone else must create the PR.

Start by locating the catalog entries for the nine failed URLs listed in the issue and checking whether each URL and schema remains available. Review the existing catalog validation or CI entry points, if present, before deciding how failures should be recorded. Done means the broken entries have a documented resolution and the catalog has a repeatable way to detect URL or schema validation failures.