Repository navigation
Add the change log entry for 20260924.2 - #512
Merged
Merged
Conversation
The release workflow turns "Next release" into the release entry and refuses to run without one. Describe what #510 changed for users, which is nothing in output: the lexer's walk keeps its bound as a second line of defence, and the nesting limit is documented as able to drop valid CSS such as a deeply nested later branch of if(). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Adds the
Next releasesection thatrelease.ymlrequires, describing #510 for users: no change in output, a defensive bound kept in the lexer's bracket walk, and the nesting limit documented as able to drop valid CSS such as a deeply nested later branch ofif().Merge before dispatching the 20260924.2 release.
🤖 Generated with Claude Code