Version Packages - #448
Merged
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
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@eventcatalog/generator-asyncapi@7.0.3
Patch Changes
64eaeb7: fix(asyncapi): escape angle brackets and curly braces in service and channel descriptions
AsyncAPI info and channel descriptions were written into the generated markdown
unescaped. A description containing angle brackets, e.g.
<fieldname>,<asc/desc>,is parsed by MDX as a JSX tag and breaks the EventCatalog build with errors like
"Unexpected character
d(U+0064) after self-closing slash, expected>to endthe tag"; curly braces are parsed as JSX expressions and fail similarly. These
characters are now escaped in service and channel descriptions, while content
inside fenced code blocks and inline code spans is left untouched.
@eventcatalog/generator-openapi@9.0.1
Patch Changes
64eaeb7: fix(openapi): escape angle brackets in parameter and schema descriptions
OpenAPI parameter and response schema descriptions were written into the
generated markdown unescaped. A description containing angle brackets, e.g.
<veldnaam>,<asc/desc>, is parsed by MDX as a JSX tag and breaks theEventCatalog build with errors like "Unexpected character
d(U+0064) afterself-closing slash, expected
>to end the tag". Angle brackets and curlybraces are now escaped in these descriptions, while content inside fenced
code blocks and inline code spans is left untouched.