fix: parse fenced docs review json - #260
Merged
Merged
Conversation
Contributor
🟠 Maintainer review suggested — low confidenceAutomated semantic review could not be completed. Limitations
This review is advisory and does not block merging. |
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.
Fixes the docs review bot's OpenAI JSON parsing for the lighter review model. The model was returning JSON wrapped in markdown, which made the advisory review path report invalid JSON.\n\nThis keeps low reasoning, removes the rejected structured-output request for this model, adds an explicit JSON-only system instruction, and accepts fenced JSON output.\n\nVerification:\n- npx vitest run src/docs-sync-review-cli.test.ts src/generate-release-notes-cli.test.ts\n- npm run typecheck