chore: relocate spec linting to the producer#7
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The lint ruleset and
lint:speccommand move to platform-api, which owns the ruleset and enforces it pre-merge (alongside the DTOs that must satisfy it). The hub reverts to a pure distribution repo: published spec, releases, changelog, and publish logic. Removes.spectral.yaml, thelint:specscript, and the@stoplight/spectral-clidevDep; updates docs.The hub never gated publishing, and no consumer re-lints the published spec, so nothing here used the ruleset at runtime. typecheck + tests still pass.