To get some json config linting & hinting you need set a $schema. This schema is published in the @changesets/config package, which is not directly installed by the consumer (making it hard to pinpoint the location, which often changes with pnpm catalogs), so consumers are best off by using https://unpkg.com/@changesets/config@4.0.0/schema.json. However, as the URL references to a version of the @changesets/config package, it also requires bumping once in a while. Which can be easily forgotten. Or mismatch from the version installed
Would it be an option to publish the schema with the cli package, so people can reference the schema using: "$schema": "./node_modules/@changesets/cli/schema.json". That way it's always tied to the version locally installed.
To get some json config linting & hinting you need set a
$schema. This schema is published in the@changesets/configpackage, which is not directly installed by the consumer (making it hard to pinpoint the location, which often changes with pnpm catalogs), so consumers are best off by usinghttps://unpkg.com/@changesets/config@4.0.0/schema.json. However, as the URL references to a version of the@changesets/configpackage, it also requires bumping once in a while. Which can be easily forgotten. Or mismatch from the version installedWould it be an option to publish the schema with the cli package, so people can reference the schema using:
"$schema": "./node_modules/@changesets/cli/schema.json". That way it's always tied to the version locally installed.