Skip to content

Update dependency prettier to v3.8.1#1665

Merged
kevinansfield merged 2 commits intomainfrom
renovate/prettier-3.x
Mar 16, 2026
Merged

Update dependency prettier to v3.8.1#1665
kevinansfield merged 2 commits intomainfrom
renovate/prettier-3.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Dec 10, 2025

This PR contains the following updates:

Package Change Age Confidence
prettier (source) 3.6.23.8.1 age confidence

Release Notes

prettier/prettier (prettier)

v3.8.1

Compare Source

v3.8.0

Compare Source

diff

🔗 Release note

v3.7.4

Compare Source

diff

LWC: Avoid quote around interpolations (#​18383 by @​kovsu)
<!-- Input -->
<div foo={bar}>   </div>

<!-- Prettier 3.7.3 (--embedded-language-formatting off) -->
<div foo="{bar}"></div>

<!-- Prettier 3.7.4 (--embedded-language-formatting off) -->
<div foo={bar}></div>
TypeScript: Fix comment inside union type gets duplicated (#​18393 by @​fisker)
// Input
type Foo = (/** comment */ a | b) | c;

// Prettier 3.7.3
type Foo = /** comment */ (/** comment */ a | b) | c;

// Prettier 3.7.4
type Foo = /** comment */ (a | b) | c;
TypeScript: Fix unstable comment print in union type comments (#​18395 by @​fisker)
// Input
type X = (A | B) & (
  // comment
  A | B
);

// Prettier 3.7.3 (first format)
type X = (A | B) &
  (// comment
  A | B);

// Prettier 3.7.3 (second format)
type X = (
  | A
  | B // comment
) &
  (A | B);

// Prettier 3.7.4
type X = (A | B) &
  // comment
  (A | B);

v3.7.3

Compare Source

diff

API: Fix prettier.getFileInfo() change that breaks VSCode extension (#​18375 by @​fisker)

An internal refactor accidentally broke the VSCode extension plugin loading.

v3.7.2

Compare Source

diff

JavaScript: Fix string print when switching quotes (#​18351 by @​fisker)
// Input
console.log("A descriptor\\'s .kind must be \"method\" or \"field\".")

// Prettier 3.7.1
console.log('A descriptor\\'s .kind must be "method" or "field".');

// Prettier 3.7.2
console.log('A descriptor\\\'s .kind must be "method" or "field".');
JavaScript: Preserve quote for embedded HTML attribute values (#​18352 by @​kovsu)
// Input
const html = /* HTML */ ` <div class="${styles.banner}"></div> `;

// Prettier 3.7.1
const html = /* HTML */ ` <div class=${styles.banner}></div> `;

// Prettier 3.7.2
const html = /* HTML */ ` <div class="${styles.banner}"></div> `;
TypeScript: Fix comment in empty type literal (#​18364 by @​fisker)
// Input
export type XXX = {
  // tbd
};

// Prettier 3.7.1
export type XXX = { // tbd };

// Prettier 3.7.2
export type XXX = {
  // tbd
};

v3.7.1

Compare Source

diff

API: Fix performance regression in doc printer (#​18342 by @​fisker)

Prettier 3.7.1 can be very slow when formatting big files, the regression has been fixed.

v3.7.0

Compare Source

diff

🔗 Release Notes


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Dec 10, 2025

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: cdd59829-e4a4-46ee-b313-3701a40f28ff

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Walkthrough

The pull request updates the Prettier devDependency from 3.6.2 to 3.8.1 in three package.json files: packages/kg-default-nodes, packages/kg-lexical-html-renderer, and packages/koenig-lexical. No other dependencies, scripts, exported declarations, or runtime functionality are changed.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately and concisely describes the main change: updating the prettier dependency to version 3.8.1 across multiple packages.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description check ✅ Passed The pull request description clearly relates to the changeset, detailing the prettier dependency update from 3.6.2 to 3.8.1 across three packages with comprehensive release notes.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch renovate/prettier-3.x
📝 Coding Plan
  • Generate coding plan for human review comments

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Tip

You can customize the tone of the review comments and chat replies.

Configure the tone_instructions setting to customize the tone of the review comments and chat replies. For example, you can set the tone to Act like a strict teacher, Act like a pirate and more.

@renovate renovate Bot force-pushed the renovate/prettier-3.x branch from 983a7e8 to 969750c Compare December 31, 2025 18:14
@renovate renovate Bot force-pushed the renovate/prettier-3.x branch from 969750c to aba9158 Compare January 8, 2026 20:55
@renovate renovate Bot force-pushed the renovate/prettier-3.x branch from aba9158 to d59e9ec Compare January 18, 2026 03:10
@renovate renovate Bot changed the title Update dependency prettier to v3.7.4 Update dependency prettier to v3.8.0 Jan 18, 2026
@renovate renovate Bot force-pushed the renovate/prettier-3.x branch 14 times, most recently from 1e491a8 to 09b44d1 Compare January 24, 2026 19:55
@renovate renovate Bot changed the title Update dependency prettier to v3.8.0 Update dependency prettier to v3.8.1 Jan 24, 2026
@renovate renovate Bot force-pushed the renovate/prettier-3.x branch 10 times, most recently from f190901 to 1f7b735 Compare January 28, 2026 09:16
@renovate renovate Bot force-pushed the renovate/prettier-3.x branch 4 times, most recently from e0964ab to f190f02 Compare February 12, 2026 15:03
@renovate renovate Bot enabled auto-merge (squash) February 12, 2026 15:03
@renovate renovate Bot force-pushed the renovate/prettier-3.x branch 5 times, most recently from 4a1e7ed to d268e3d Compare February 12, 2026 19:52
@ErisDS
Copy link
Copy Markdown
Member

ErisDS commented Mar 2, 2026

🤖 Velo CI Failure Analysis

Classification: 🟠 SOFT FAIL

  • Workflow: Test
  • Failed Step: Run yarn test
  • Run: View failed run
    What failed: Lerna test target failed for @tryghost/kg-default-nodes package
    Why: The final error in the logs indicates that the Lerna test target failed for the @tryghost/kg-default-nodes package. This is a code issue, as the failure is likely due to a problem with the code in that package, such as a test assertion failure or a missing dependency.
    Action:
    The author should investigate the failure in the @tryghost/kg-default-nodes package, fix any issues in the code, and re-run the tests to ensure the issue is resolved.

@ErisDS
Copy link
Copy Markdown
Member

ErisDS commented Mar 2, 2026

🤖 Velo CI Failure Analysis

Classification: 🟠 SOFT FAIL

  • Workflow: Test
  • Failed Step: Run yarn test
  • Run: View failed run
    What failed: Lerna test target failed for @tryghost/kg-default-nodes package
    Why: The final error in the logs indicates that the Lerna test target failed for the @tryghost/kg-default-nodes package. This is a code issue, as the failure is likely due to a problem with the code in that package, such as a test assertion failure or a missing dependency.
    Action:
    The author should investigate the failure in the @tryghost/kg-default-nodes package, fix the underlying code issue, and re-run the tests.

@ErisDS
Copy link
Copy Markdown
Member

ErisDS commented Mar 2, 2026

🤖 Velo CI Failure Analysis

Classification: 🟠 SOFT FAIL

  • Workflow: Test
  • Failed Step: Run yarn test
  • Run: View failed run
    What failed: Lerna test target failed for @tryghost/kg-default-nodes package
    Why: The final error in the logs indicates that the Lerna test target failed for the @tryghost/kg-default-nodes package. This is likely a code issue, as the error does not point to any infrastructure-related problems.
    Action:
    The author should investigate the test failures in the @tryghost/kg-default-nodes package and fix any issues in the code to resolve the CI failure.

@ErisDS
Copy link
Copy Markdown
Member

ErisDS commented Mar 3, 2026

🤖 Velo CI Failure Analysis

Classification: 🟠 SOFT FAIL

  • Workflow: Test
  • Failed Step: Run yarn test
  • Run: View failed run
    What failed: Lerna test target failed for @tryghost/kg-default-nodes package
    Why: The final error in the logs indicates that the Lerna test target failed for the @tryghost/kg-default-nodes package. This is a code issue, as the failure is likely due to a problem with the code in that package, such as a test assertion failure or a missing dependency.
    Action:
    The author should investigate the failure in the @tryghost/kg-default-nodes package, fix any issues in the code, and re-run the tests to ensure the issue is resolved.

@ErisDS
Copy link
Copy Markdown
Member

ErisDS commented Mar 3, 2026

🤖 Velo CI Failure Analysis

Classification: 🟠 SOFT FAIL

  • Workflow: Test
  • Failed Step: Run yarn test
  • Run: View failed run
    What failed: Lerna test target failed for @tryghost/kg-default-nodes package
    Why: The final error in the logs indicates that the Lerna test target failed for the @tryghost/kg-default-nodes package. This is a code issue, as the failure is likely due to a problem with the code in that package, such as a test assertion failure or a missing dependency.
    Action:
    The author should investigate the tests and code in the @tryghost/kg-default-nodes package to identify and fix the issue that caused the test failure.

@ErisDS
Copy link
Copy Markdown
Member

ErisDS commented Mar 3, 2026

🤖 Velo CI Failure Analysis

Classification: 🟠 SOFT FAIL

  • Workflow: Test
  • Failed Step: Run yarn test
  • Run: View failed run
    What failed: Lerna test target failed for @tryghost/kg-default-nodes package
    Why: The final error in the logs indicates that the Lerna test target failed for the @tryghost/kg-default-nodes package. This is a code issue, as the failure is likely due to a problem with the code in that package, such as a test assertion failure or a missing dependency.
    Action:
    The author should investigate the failure in the @tryghost/kg-default-nodes package, fix any issues in the code, and re-run the tests to ensure the issue is resolved.

@ErisDS
Copy link
Copy Markdown
Member

ErisDS commented Mar 3, 2026

🤖 Velo CI Failure Analysis

Classification: 🟠 SOFT FAIL

  • Workflow: Test
  • Failed Step: Run yarn test
  • Run: View failed run
    What failed: Lerna test target failed for @tryghost/kg-default-nodes package
    Why: The final error in the logs indicates that the Lerna test target failed for the @tryghost/kg-default-nodes package. This is a code issue, as the failure is likely due to a problem with the code in that specific package.
    Action:
    The author should investigate the test failures in the @tryghost/kg-default-nodes package and fix any issues in the code to resolve the CI failure.

@ErisDS
Copy link
Copy Markdown
Member

ErisDS commented Mar 3, 2026

🤖 Velo CI Failure Analysis

Classification: 🟠 SOFT FAIL

  • Workflow: Test
  • Failed Step: Run yarn test
  • Run: View failed run
    What failed: Lerna test target failed for @tryghost/kg-default-nodes package
    Why: The final error in the logs indicates that the Lerna test target failed for the @tryghost/kg-default-nodes package. This is a code issue, as the failure is likely due to a problem with the code in that package, such as a test assertion failure or a missing dependency.
    Action:
    The author should investigate the test failures in the @tryghost/kg-default-nodes package and fix any issues in the code to resolve the CI failure.

@ErisDS
Copy link
Copy Markdown
Member

ErisDS commented Mar 4, 2026

🤖 Velo CI Failure Analysis

Classification: 🟠 SOFT FAIL

  • Workflow: Test
  • Failed Step: Run yarn test
  • Run: View failed run
    What failed: Lerna test target failed for @tryghost/kg-default-nodes package
    Why: The final error in the logs indicates that the Lerna test target failed for the @tryghost/kg-default-nodes package. This is a code issue, as the failure is likely due to a problem with the code in that package, such as a test assertion failure or a missing dependency.
    Action:
    The author should investigate the failure in the @tryghost/kg-default-nodes package, fix any issues in the code, and re-run the tests to ensure the issue is resolved.

@ErisDS
Copy link
Copy Markdown
Member

ErisDS commented Mar 15, 2026

🤖 Velo CI Failure Analysis

Classification: 🟠 SOFT FAIL

  • Workflow: Test
  • Failed Step: Run yarn test
  • Run: View failed run
    What failed: CI failure - likely code issue
    Why: The failure appears to be related to code changes. Check the error output for details.
    Action:
    Review the error logs and fix the issue in your code.

@ErisDS
Copy link
Copy Markdown
Member

ErisDS commented Mar 16, 2026

🤖 Velo CI Failure Analysis

Classification: 🟠 SOFT FAIL

  • Workflow: Test
  • Failed Step: Run yarn test
  • Run: View failed run
    What failed: CI failure - likely code issue
    Why: The failure appears to be related to code changes. Check the error output for details.
    Action:
    Review the error logs and fix the issue in your code.

@ErisDS
Copy link
Copy Markdown
Member

ErisDS commented Mar 16, 2026

🤖 Velo CI Failure Analysis

Classification: 🟠 SOFT FAIL

  • Workflow: Test
  • Failed Step: Run yarn test
  • Run: View failed run
    What failed: CI failure - likely code issue
    Why: The failure appears to be related to code changes. Check the error output for details.
    Action:
    Review the error logs and fix the issue in your code.

@ErisDS
Copy link
Copy Markdown
Member

ErisDS commented Mar 16, 2026

🤖 Velo CI Failure Analysis

Classification: 🟠 SOFT FAIL

  • Workflow: Test
  • Failed Step: Run yarn test
  • Run: View failed run
    What failed: CI failure - likely code issue
    Why: The failure appears to be related to code changes. Check the error output for details.
    Action:
    Review the error logs and fix the issue in your code.

@ErisDS
Copy link
Copy Markdown
Member

ErisDS commented Mar 16, 2026

🤖 Velo CI Failure Analysis

Classification: 🟠 SOFT FAIL

  • Workflow: Test
  • Failed Step: Run yarn test
  • Run: View failed run
    What failed: CI failure - likely code issue
    Why: The failure appears to be related to code changes. Check the error output for details.
    Action:
    Review the error logs and fix the issue in your code.

@ErisDS
Copy link
Copy Markdown
Member

ErisDS commented Mar 16, 2026

🤖 Velo CI Failure Analysis

Classification: 🟠 SOFT FAIL

  • Workflow: Test
  • Failed Step: Run yarn test
  • Run: View failed run
    What failed: CI failure - likely code issue
    Why: The failure appears to be related to code changes. Check the error output for details.
    Action:
    Review the error logs and fix the issue in your code.

@ErisDS
Copy link
Copy Markdown
Member

ErisDS commented Mar 16, 2026

🤖 Velo CI Failure Analysis

Classification: 🟠 SOFT FAIL

  • Workflow: Test
  • Failed Step: Run yarn test
  • Run: View failed run
    What failed: CI failure - likely code issue
    Why: The failure appears to be related to code changes. Check the error output for details.
    Action:
    Review the error logs and fix the issue in your code.

@ErisDS
Copy link
Copy Markdown
Member

ErisDS commented Mar 16, 2026

🤖 Velo CI Failure Analysis

Classification: 🟠 SOFT FAIL

  • Workflow: Test
  • Failed Step: Run yarn test
  • Run: View failed run
    What failed: CI failure - likely code issue
    Why: The failure appears to be related to code changes. Check the error output for details.
    Action:
    Review the error logs and fix the issue in your code.

renovate Bot and others added 2 commits March 16, 2026 11:16
Prettier 3.8.1 reformats iframe `allow` attribute values with newlines
and semicolons. The test input goes through prettier via the `html`
template tag, but the assertions used `.should.equal()` with raw strings.
Switching to `.should.prettifyTo()` normalizes both sides through prettier,
making the comparison semantic rather than whitespace-dependent.
@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Mar 16, 2026

Edited/Blocked Notification

Renovate 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.

⚠️ Warning: custom changes will be lost.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants