fix(deps): update dependency comment-json to v5 - #8471
Merged
Conversation
renovate
Bot
added
dependencies
renovate
Bot
added
dependencies
commit: |
![kodiakhq[bot]](https://avatars.githubusercontent.com/in/29196?s=60&v=4){kind=small}
serhalp
enabled auto-merge (squash)
September 4, 2026 13:44
serhalp
approved these changes
Sep 4, 2026
Contributor
Author
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
serhalp
pushed a commit
that referenced
this pull request
Sep 4, 2026
🤖 I have created a release *beep* *boop* --- ## [27.5.0](v27.4.3...v27.5.0) (2026-09-04) ### Features * **clone:** support Netlify managed git service ([#8437](#8437)) ([4476e10](4476e10)) * **logs:** add --deploy-id flag to target a specific deploy ([28e44be](28e44be)) ### Bug Fixes * **deps:** update dependency chalk to v6 ([#8470](#8470)) ([9ebe398](9ebe398)) * **deps:** update dependency comment-json to v5 ([#8471](#8471)) ([f458d83](f458d83)) * **logs:** auto-select the latest finished deploy, including failures ([b312e2d](b312e2d)) * **logs:** close the deploy stream when replaying a finished deploy ([8b84c92](8b84c92)) * **logs:** fetch historical deploy logs over websocket ([783c3d9](783c3d9)) * **logs:** keep the deploy stream resilient to failed state checks ([d874293](d874293)) * **logs:** stream the targeted deploy in --follow ([d04b659](d04b659)) * stop publishing source maps ([#8468](#8468)) ([3282dab](3282dab)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: token-generator-app[bot] <82042599+token-generator-app[bot]@users.noreply.github.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
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.
This PR contains the following updates:
^4.6.2→^5.0.0Release Notes
kaelzhang/node-comment-json (comment-json)
v5.0.0Compare Source
MAJOR: blank lines are now modeled explicitly instead of being inferred from
locand historical line-break logic.BlankLinecomment tokens and use them duringparse()/stringify().parse(code, reviver, { no_comments, no_blank_lines }).removeBlankLines()for removing blank lines globally or at a specific comment location.Potential breaking changes
This release may introduce breaking changes for consumers who directly inspect or mutate comment tokens:
CommentTokenis now a union type. A token may be{ type: 'BlankLine', inline: false }, sovalueandlocare no longer guaranteed on every token.stringify()no longer useslocor the old internal blank-line history to infer empty lines. Blank lines are rendered only from explicitBlankLinetokens.Behavior differences
If your existing usage includes business logic related to blank lines, you may notice behavior differences:
loc-based blank-line rendering may now produce different output unless it preservesBlankLinetokens explicitly.BlankLine.{ no_blank_lines: true }now provides an explicit way to drop blank lines, while default parsing preserves them as first-class tokens.An upgrade review is recommended for dependents that have custom comment-token processing or formatting logic around blank lines.
Configuration
📅 Schedule: (UTC)
* 0-3 * * 1)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.