Bump spectral-core version#675
Closed
kornel-kotan-sonarsource wants to merge 1 commit into
Closed
Conversation
|
Thanks for this! Hope we can get this sorted asap! |
emma-patterson-sonarsource
approved these changes
Jul 16, 2025
Contributor
|
This should be fixed here https://github.com/stoplightio/spectral-action/releases/tag/v0.8.13 @kornel-kotan-sonarsource |
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
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.
Motivation and Context
This change is required to fix compilation errors that occur when HTTP response codes are defined as numbers instead of strings in OpenAPI specifications. The issue was present in spectral-core version 1.18.x and has been resolved in version 1.20.0.
Related issue: stoplightio/spectral#955
Description
Updated
@stoplight/spectral-coredependency from version^1.18.3to^1.20.0in package.json. This version includes fixes for handling HTTP response codes defined as numbers in OpenAPI specifications, which previously caused compilation errors.The update ensures compatibility with OpenAPI specifications that use numeric response codes (e.g.,
200,404) instead of string representations (e.g.,"200","404").How Has This Been Tested?
npm installnpm run build- no compilation errorsCode reviewers can verify the changes by:
npm run buildto ensure TypeScript compilation succeedsScreenshot(s)/recordings(s)
Not applicable - this is a dependency update.
Types of changes
Checklist