[dependabot]

Bumps the npm-version group with 10 updates:

Package	From	To
@tailwindcss/vite	4.3.4	4.3.5
ckeditor5	49.0.1	49.1.0
concurrently	10.0.6	10.0.7
laravel-vite-plugin	3.2.0	3.2.1
mermaid	12.2.0	12.3.0
playwright	1.64.1	1.65.0
tailwindcss	4.3.4	4.3.5
@rollup/rollup-linux-x64-gnu	4.67.4	4.68.0
@tailwindcss/oxide-linux-x64-gnu	4.3.4	4.3.5
vite-plus	1.4.0	1.5.0

Updates @tailwindcss/vite from 4.3.4 to 4.3.5

Release notes

Sourced from @​tailwindcss/vite's releases.

v4.3.5

Fixed

• Canonicalization: improve performance in projects with many functional variant values (e.g. a matchVariant plugin with thousands of values) (#20663)
• Don't crash or create a fallback with the wrong color for a color-mix(…) without a color interpolation method (e.g. color-mix(var(--color-red-500)) or color-mix(currentcolor 50%, transparent)) (#20658, #20666)
• Ensure @tailwindcss/oxide-wasm32-wasi loads instead of hanging forever (e.g. with NAPI_RS_FORCE_WASI=error or in WebContainers) (#20667)
• Remove as: '*.css' from the @tailwindcss/turbopack setup in its README, because it breaks CSS modules (#20660)
• Ignore <!-- and --> between top-level rules in CSS instead of throwing or swallowing the next rule (e.g. a { color: red } --> b { color: blue }) (#20665)
• Ensure @tailwindcss/oxide-wasm32-wasi detects changed and new source files after the first scan (e.g. in WebContainers) (#20487)
• Prevent type errors with skipLibCheck: false caused by imports of unshipped modules in the @tailwindcss/node type declarations (#20632)

Changelog

Sourced from @​tailwindcss/vite's changelog.

[4.3.5] - 2026-11-06

Fixed

• Canonicalization: improve performance in projects with many functional variant values (e.g. a matchVariant plugin with thousands of values) (#20663)
• Don't crash or create a fallback with the wrong color for a color-mix(…) without a color interpolation method (e.g. color-mix(var(--color-red-500)) or color-mix(currentcolor 50%, transparent)) (#20658, #20666)
• Ensure @tailwindcss/oxide-wasm32-wasi loads instead of hanging forever (e.g. with NAPI_RS_FORCE_WASI=error or in WebContainers) (#20667)
• Remove as: '*.css' from the @tailwindcss/turbopack setup in its README, because it breaks CSS modules (#20660)
• Ignore <!-- and --> between top-level rules in CSS instead of throwing or swallowing the next rule (e.g. a { color: red } --> b { color: blue }) (#20665)
• Ensure @tailwindcss/oxide-wasm32-wasi detects changed and new source files after the first scan (e.g. in WebContainers) (#20487)
• Prevent type errors with skipLibCheck: false caused by imports of unshipped modules in the @tailwindcss/node type declarations (#20632)

Commits

• 9b2c925 4.3.5 (#20672)
• See full diff in compare view

Updates ckeditor5 from 49.0.1 to 49.1.0

Release notes

Sourced from ckeditor5's releases.

v49.1.0

We are happy to announce the release of CKEditor 5 v49.1.0.

Release highlights

⭐ Editing Toolkit

We are releasing Editing Toolkit, a new set of APIs for developers who build their own editing experiences.

Editing Toolkit grew out of our work on CKEditor AI, our plug-and-play AI offering. Turn it on, and you have an editor with AI that keeps humans in the loop.

But some teams want to build their own AI integration rather than use a ready-made one. Editing Toolkit gives them the building blocks to work with content in the editor. It consists of two parts:

• Compare: an editor API that lets you compare two versions of HTML content, then apply or suggest individual changes. You can also preview the changes before they land in the content.
• Coauthor: think of it as MCP for CKEditor. It lets server-side agents draft content, suggest edits, or leave comments in the editor: through ChatGPT or Claude, or as background jobs. Coauthor is currently in early access, and if you would like to test it, let us know.

Editing Toolkit is not limited to AI. You can also use it in strictly deterministic scenarios like manipulating content with code or comparing it with externally generated HTML, for example, HTML converted from an updated Word file.

⭐ CKEditor AI: custom skills for your features

CKEditor AI can now work with the content of your plugins, such as a custom widget or a new HTML element. Upload a custom skill that describes the markup and rules of your feature, then register the plugin with AIEditorConfig#add(). The AI agent then writes and keeps your custom content in the shape your editor accepts, and its proposed changes follow your feature's rules.

See Registering custom features for details.

⭐ CKEditor AI: hooks for your agent and policies

On-premises deployments of CKEditor AI can call a service you host before the agent answers an AI Chat message. With hooks, your service can check each message against your policies, answer from your systems, or pass context and instructions to the CKEditor AI agent. Use them when you already have an AI platform with access to your data and want it to take part in the chat.

⭐ Editor bundle for Cloud Services with your AI coding agent

Coauthor runs your editor on the server, so it needs an editor bundle uploaded to Cloud Services. It joins the other features that require the editor bundle. The new ckeditor-bundle skill lets your AI coding agent set it up. It moves the editor into one module that both your application and the bundle use, adds the bundle build for your bundler, checks the bundle with test data, and adds the upload scripts for your CI.

Two new guides come with the skill. Editor bundling with Vite shows how to share one editor definition between your application and the bundle. Testing the editor bundle with test data explains how Cloud Services checks the bundle and how to fix a failed upload.

Other improvements and fixes

• New theme improvements and fixes: v49.0.0 introduced a refreshed default theme built on three layers of design tokens (foundation scales, semantic roles, and per-component tokens), with legacy variable names kept as aliases. Some aliases were silently ignored even though the migration guide said they worked. They work again, so overrides of focus borders and the shadows of dropdowns, balloons, menus, and comment and suggestion cards apply with no changes on your side. Additionally, more of the UI moved from hard-coded values to tokens (#20255, #20257, #20259): button colors in the resting, hover, and active states, toolbar button borders and radius, form and dialog headers, the insert table grid, and find and replace results. Every new token defaults to the value used today, so the default theme looks the same. See the full token list in the theme customization guide.
• Shadow DOM support for more features: the CKBox file manager and image editor, the "Edit source" dialog of enhanced source editing, and footnotes work correctly when the editor renders in a shadow root. Plugin authors get two helpers for events that do not cross a shadow boundary, such as scroll: listenToEventRoots() listens on the document and on every shadow root the editor lives in, and DomTargetsListener listens on a set of targets you can refresh, like a balloon's positioning target. See the Shadow DOM deep dive.
• More reliable balloons and toolbars: tooltips, the link balloon, and the mention list appear in the right place again on scrolled pages when <body> or the overlay container is positioned (a v49.0.0 regression, #20251).
• Content loading: some browsers started parsing <?target data?> markup as processing instruction nodes instead of comments, which made the editor throw while loading or pasting such content. The editor ignores these nodes the same way it ignores comments, and data processors have a new skipProcessingInstructions flag for integrations that need to keep them.
• Email export fixes: Email export converts hsl() and hsla() colors to rgb() and rgba() through the new transformEmailStylesColors() transformation, since many email clients, including Outlook, do not support HSL. The default font and table palettes also no longer trigger warnings in the email configuration logger.

MINOR BREAKING CHANGES ℹ️

• collaboration-core, comments: Focused comments and suggestions are now marked with a focus ring instead of a background color. The --ck-comment-focus-background-color and --ck-suggestion-box-focus-background-color CSS variables have been removed. To style the focus ring, use the new --ck-comment-focus-border-color, --ck-comment-focus-shadow, --ck-suggestion-box-focus-border-color, and --ck-suggestion-box-focus-shadow CSS variables.
• ai: The AIEditorConfig type describing the editor configuration snapshot has been renamed to AIEditorConfigSnapshot. The AIEditorConfig name now refers to the new plugin that produces the snapshot and registers custom features. If you used the AIEditorConfig type (for example, to type DocumentCompareSnapshot#editorConfig or AIEditingDocumentData#editorConfig), replace it with AIEditorConfigSnapshot.
• comments: The default CommentThreadView no longer renders the comment thread header, and the BaseCommentThreadView#commentThreadHeaderView property is deprecated. Customizations of the header, such as buttons added to it or styles for the .ck-thread__header and .ck-context CSS classes, no longer apply. The reopen button is now available in the first comment as CommentThreadView#reopenButton. If you need the header, add commentThreadHeaderView to the template of your custom comment thread view.
• comments: The --ck-comment-input-padding CSS variable now sets only the padding of the comment field container, not the padding inside the comment field. If you used it to change the padding inside the comment field, use the new --ck-comment-input-field-padding CSS variable instead.
• revision-history: Some Revision History CSS variables now style different parts of the refreshed sidebar:

... (truncated)

Changelog

Sourced from ckeditor5's changelog.

49.1.0 (November 4, 2026)

We are happy to announce the release of CKEditor 5 v49.1.0.

Release highlights

⭐ Editing Toolkit

We are releasing Editing Toolkit, a new set of APIs for developers who build their own editing experiences.

Editing Toolkit grew out of our work on CKEditor AI, our plug-and-play AI offering. Turn it on, and you have an editor with AI that keeps humans in the loop.

But some teams want to build their own AI integration rather than use a ready-made one. Editing Toolkit gives them the building blocks to work with content in the editor. It consists of two parts:

• Compare: an editor API that lets you compare two versions of HTML content, then apply or suggest individual changes. You can also preview the changes before they land in the content.
• Coauthor: think of it as MCP for CKEditor. It lets server-side agents draft content, suggest edits, or leave comments in the editor: through ChatGPT or Claude, or as background jobs. Coauthor is currently in early access, and if you would like to test it, let us know.

Editing Toolkit is not limited to AI. You can also use it in strictly deterministic scenarios like manipulating content with code or comparing it with externally generated HTML, for example, HTML converted from an updated Word file.

⭐ CKEditor AI: custom skills for your features

CKEditor AI can now work with the content of your plugins, such as a custom widget or a new HTML element. Upload a custom skill that describes the markup and rules of your feature, then register the plugin with AIEditorConfig#add(). The AI agent then writes and keeps your custom content in the shape your editor accepts, and its proposed changes follow your feature's rules.

See Registering custom features for details.

⭐ CKEditor AI: hooks for your agent and policies

On-premises deployments of CKEditor AI can call a service you host before the agent answers an AI Chat message. With hooks, your service can check each message against your policies, answer from your systems, or pass context and instructions to the CKEditor AI agent. Use them when you already have an AI platform with access to your data and want it to take part in the chat.

⭐ Editor bundle for Cloud Services with your AI coding agent

Coauthor runs your editor on the server, so it needs an editor bundle uploaded to Cloud Services. It joins the other features that require the editor bundle. The new ckeditor-bundle skill lets your AI coding agent set it up. It moves the editor into one module that both your application and the bundle use, adds the bundle build for your bundler, checks the bundle with test data, and adds the upload scripts for your CI.

Two new guides come with the skill. Editor bundling with Vite shows how to share one editor definition between your application and the bundle. Testing the editor bundle with test data explains how Cloud Services checks the bundle and how to fix a failed upload.

Other improvements and fixes

• New theme improvements and fixes: v49.0.0 introduced a refreshed default theme built on three layers of design tokens (foundation scales, semantic roles, and per-component tokens), with legacy variable names kept as aliases. Some aliases were silently ignored even though the migration guide said they worked. They work again, so overrides of focus borders and the shadows of dropdowns, balloons, menus, and comment and suggestion cards apply with no changes on your side. Additionally, more of the UI moved from hard-coded values to tokens (#20255, #20257, #20259): button colors in the resting, hover, and active states, toolbar button borders and radius, form and dialog headers, the insert table grid, and find and replace results. Every new token defaults to the value used today, so the default theme looks the same. See the full token list in the theme customization guide.
• Shadow DOM support for more features: the CKBox file manager and image editor, the "Edit source" dialog of enhanced source editing, and footnotes work correctly when the editor renders in a shadow root. Plugin authors get two helpers for events that do not cross a shadow boundary, such as scroll: listenToEventRoots() listens on the document and on every shadow root the editor lives in, and DomTargetsListener listens on a set of targets you can refresh, like a balloon's positioning target. See the Shadow DOM deep dive.
• More reliable balloons and toolbars: tooltips, the link balloon, and the mention list appear in the right place again on scrolled pages when <body> or the overlay container is positioned (a v49.0.0 regression, #20251).
• Content loading: some browsers started parsing <?target data?> markup as processing instruction nodes instead of comments, which made the editor throw while loading or pasting such content. The editor ignores these nodes the same way it ignores comments, and data processors have a new skipProcessingInstructions flag for integrations that need to keep them.
• Email export fixes: Email export converts hsl() and hsla() colors to rgb() and rgba() through the new transformEmailStylesColors() transformation, since many email clients, including Outlook, do not support HSL. The default font and table palettes also no longer trigger warnings in the email configuration logger.

MINOR BREAKING CHANGES ℹ️

• collaboration-core, comments: Focused comments and suggestions are now marked with a focus ring instead of a background color. The --ck-comment-focus-background-color and --ck-suggestion-box-focus-background-color CSS variables have been removed. To style the focus ring, use the new --ck-comment-focus-border-color, --ck-comment-focus-shadow, --ck-suggestion-box-focus-border-color, and --ck-suggestion-box-focus-shadow CSS variables.
• ai: The AIEditorConfig type describing the editor configuration snapshot has been renamed to AIEditorConfigSnapshot. The AIEditorConfig name now refers to the new plugin that produces the snapshot and registers custom features. If you used the AIEditorConfig type (for example, to type DocumentCompareSnapshot#editorConfig or AIEditingDocumentData#editorConfig), replace it with AIEditorConfigSnapshot.
• comments: The default CommentThreadView no longer renders the comment thread header, and the BaseCommentThreadView#commentThreadHeaderView property is deprecated. Customizations of the header, such as buttons added to it or styles for the .ck-thread__header and .ck-context CSS classes, no longer apply. The reopen button is now available in the first comment as CommentThreadView#reopenButton. If you need the header, add commentThreadHeaderView to the template of your custom comment thread view.
• comments: The --ck-comment-input-padding CSS variable now sets only the padding of the comment field container, not the padding inside the comment field. If you used it to change the padding inside the comment field, use the new --ck-comment-input-field-padding CSS variable instead.
• revision-history: Some Revision History CSS variables now style different parts of the refreshed sidebar:

... (truncated)

Commits

• 6573893 Release v49.1.0.
• ddbe82f Updated documentation for the v49.1.0 release.
• 9c2e503 Changelog for v49.1.0.
• 339fc62 Updated several feature packages to use semantic color tokens instead of foun...
• 2d6d6eb Fixed theme token overrides not reaching several UI components.
• 1c92c4f Fixed the results counter display in the find and replace form.
• 16c30e2 Added new CSS custom properties for theming shadow and border details.
• c3bc61d Added theming tokens for the open state of list item buttons.
• e9b2209 Added a CSS custom property to theme the editing area background.
• 2c9e23f Adjusted --ck-form-header-text-color to also apply to the header icon and h...
• Additional commits viewable in compare view

Updates concurrently from 10.0.6 to 10.0.7

Release notes

Sourced from concurrently's releases.

v10.0.7

What's Changed

• fix: log failed input writes instead of crashing by @​fzakaria in open-cli-tools/concurrently#631
• fix: flush grouped output after spawn errors by @​mithilkatkoria in open-cli-tools/concurrently#634
• fix: forward signals to the teardown command by @​fzakaria in open-cli-tools/concurrently#630
• fix: don't treat an empty command name as an input target by @​NgoQuocViet2001 in open-cli-tools/concurrently#640

New Contributors

• @​fzakaria made their first contribution in open-cli-tools/concurrently#631
• @​mithilkatkoria made their first contribution in open-cli-tools/concurrently#634
• @​NgoQuocViet2001 made their first contribution in open-cli-tools/concurrently#640

Full Changelog: open-cli-tools/concurrently@v10.0.6...v10.0.7

Commits

• f7812ab 10.0.7
• 85e096a fix: don't treat an empty command name as an input target (#640)
• 2a80d44 fix: forward signals to the teardown command (#630)
• 19bda02 fix: flush grouped output after spawn errors (#634)
• 3ec91b2 deps: upgrade non-typescript dev deps
• 6880e55 fix: log failed input writes instead of crashing (#631)
• See full diff in compare view

Updates laravel-vite-plugin from 3.2.0 to 3.2.1

Release notes

Sourced from laravel-vite-plugin's releases.

v3.2.1

What's Changed

• Bump the github-actions group with 3 updates by @​dependabot[bot] in laravel/vite-plugin#391
• Bump the github-actions group with 3 updates by @​dependabot[bot] in laravel/vite-plugin#392
• Bump the github-actions group with 3 updates by @​dependabot[bot] in laravel/vite-plugin#393
• Bump the github-actions group with 3 updates by @​dependabot[bot] in laravel/vite-plugin#395
• Bump the github-actions group with 3 updates by @​dependabot[bot] in laravel/vite-plugin#396
• Bump the github-actions group with 3 updates by @​dependabot[bot] in laravel/vite-plugin#397
• Bump the github-actions group with 3 updates by @​dependabot[bot] in laravel/vite-plugin#399
• Remove security policy in favor of the org-wide default by @​pushpak1300 in laravel/vite-plugin#400
• Bump the github-actions group with 4 updates by @​dependabot[bot] in laravel/vite-plugin#401
• Bump the github-actions group with 3 updates by @​dependabot[bot] in laravel/vite-plugin#403
• Bump the github-actions group with 3 updates by @​dependabot[bot] in laravel/vite-plugin#404
• [3.x] Allow fontaine v1 by @​intrepidws in laravel/vite-plugin#398

New Contributors

• @​pushpak1300 made their first contribution in laravel/vite-plugin#400
• @​intrepidws made their first contribution in laravel/vite-plugin#398

Full Changelog: laravel/vite-plugin@v3.2.0...v3.2.1

Changelog

Sourced from laravel-vite-plugin's changelog.

v3.2.1 - 2026-11-04

What's Changed

• Bump the github-actions group with 3 updates by @​dependabot[bot] in laravel/vite-plugin#391
• Bump the github-actions group with 3 updates by @​dependabot[bot] in laravel/vite-plugin#392
• Bump the github-actions group with 3 updates by @​dependabot[bot] in laravel/vite-plugin#393
• Bump the github-actions group with 3 updates by @​dependabot[bot] in laravel/vite-plugin#395
• Bump the github-actions group with 3 updates by @​dependabot[bot] in laravel/vite-plugin#396
• Bump the github-actions group with 3 updates by @​dependabot[bot] in laravel/vite-plugin#397
• Bump the github-actions group with 3 updates by @​dependabot[bot] in laravel/vite-plugin#399
• Remove security policy in favor of the org-wide default by @​pushpak1300 in laravel/vite-plugin#400
• Bump the github-actions group with 4 updates by @​dependabot[bot] in laravel/vite-plugin#401
• Bump the github-actions group with 3 updates by @​dependabot[bot] in laravel/vite-plugin#403
• Bump the github-actions group with 3 updates by @​dependabot[bot] in laravel/vite-plugin#404
• [3.x] Allow fontaine v1 by @​intrepidws in laravel/vite-plugin#398

New Contributors

• @​pushpak1300 made their first contribution in laravel/vite-plugin#400
• @​intrepidws made their first contribution in laravel/vite-plugin#398

Full Changelog: laravel/vite-plugin@v3.2.0...v3.2.1

Commits

• 37bd439 v3.2.1
• 284ea74 Allow fontaine v1 (#398)
• 38d2a7c Bump the github-actions group with 3 updates (#404)
• e3cba92 Bump the github-actions group with 3 updates (#403)
• 9565948 Bump the github-actions group with 4 updates (#401)
• b282bd7 Merge pull request #400 from laravel/security-policy-parity
• c034ef5 Bump the github-actions group with 3 updates (#399)
• 891d274 Bump the github-actions group with 3 updates (#397)
• db98073 Bump the github-actions group with 3 updates (#396)
• 92c60c8 Bump the github-actions group with 3 updates (#395)
• Additional commits viewable in compare view

Updates mermaid from 12.2.0 to 12.3.0

Release notes

Sourced from mermaid's releases.

mermaid@12.3.0

Minor Changes

• #8164 592d0e4 Thanks @​filipsajdak! - feat: add the open-arrow and hollow-circle edge markers, so a notation can tell two kinds of flow apart by whether the head is filled

• #8165 5c8aa5d Thanks @​filipsajdak! - feat: add the BPMN element shapes - events, gateways, activities, data objects, data stores and text annotations - each reporting where a line meets what is drawn

• #8470 692d22a Thanks @​openmindednewby! - feat: flowchart edges accept a step number (e1@{ step: 1 }); a dot travels the edges in step order and loops, hidden under prefers-reduced-motion

• #8478 56aa105 Thanks @​openmindednewby! - feat: add flowchart.stepDuration to set how many seconds each step of the flowchart step animation lasts

• #8479 800f7ef Thanks @​openmindednewby! - feat: highlight the flowchart edge whose step is playing, in sync with the step animation dot

• #8480 50d6294 Thanks @​openmindednewby! - feat: add flowchart.stepNumbers to show each step edge's number in a badge

Patch Changes

• #8443 2ff8286 Thanks @​knsv-bot! - fix: agentflow renders the a[/…/] short form as an input instead of falling back to a task with a SHAPE_UNSUPPORTED warning

• #8661 b200b27 Thanks @​pbrolin47! - fix: Bump DOMPurify to 3.4.17 to address GHSA-55q2-fjhq-7xh7 and GHSA-6688-9rhm-gjv2

• #8633 686f350 Thanks @​sidharthv96! - chore: Remove the uuid dependency and the unused legacy ER diagram renderer

• #8661 7eec083 Thanks @​pbrolin47! - fix: Stop an edge from a node inside a subgraph from crossing an edge from the subgraph itself to the same node with ELK 0.10+ (e.g. outer --> a with da --> a, or three --> two with two --> c2)

• #8532 42d3760 Thanks @​Devehab! - fix: upgrade bundled elkjs from 0.9.3 to 0.12.0, which is licensed EPL-2.0 OR GPL-3.0-or-later, so GPL-3.0 projects can ship mermaid with ELK

• #8162 d5ca27a Thanks @​filipsajdak! - fix(swimlanes): size a lane that holds a nested subgraph (TB drew it as an empty 0x0 box, and likewise an outer group holding lanes), and grow LR and RL lanes by the nested group's padding

• #8405 b4299f2 Thanks @​filipsajdak! - fix: do not draw a stray empty swimlane when a node is listed in two lanes, and warn about it and about a subgraph nested in a lane

• #8385 37d0ace Thanks @​filipsajdak! - fix(swimlanes): keep two arrowheads that land on one face of a node apart when a sibling edge is straightened

• #8385 38e810a Thanks @​filipsajdak! - fix(swimlanes): an edge routed round the outside of a diamond now arrives at one of its vertices instead of ending in empty space beside it

• #8385 25d7e31 Thanks @​filipsajdak! - fix(swimlanes): a second edge leaving a diamond on the same level as its target now leaves from a free vertex instead of running beside the first

• #8171 a4750b4 Thanks @​filipsajdak! - fix: dock a swimlane edge on the shape it points at, so a line reaches an event's ring instead of stopping at the room its caption reserves

• #8385 67315b9 Thanks @​filipsajdak! - fix: an edge label no longer pushes the nodes it joins a rank apart

• #8385 21a1f5c Thanks @​filipsajdak! - fix(swimlanes): stop the crossing cleanup from joining two routes at a corner so they read as one line

• #8385 e14bc3a Thanks @​filipsajdak! - fix(swimlanes): an edge no longer arrives at the vertex of a hexagon that another edge leaves from

• #8459 edd162f Thanks @​Yun-seoung! - fix: Allow flowchart edge IDs regardless of whitespace after the node shape

  Edge IDs may no longer contain [ ] ( ) { } |.

• #8402 4f2bade Thanks @​pcp-cmd! - fix: Render use case include and extend relationship labels with UML guillemets.

Commits

• 2086904 Merge pull request #8671 from mermaid-js/changeset-release/master
• 41781cb Version Packages
• 30b486a Merge pull request #8661 from mermaid-js/release/12.3.0
• 86340ba docs: set the release version for the flowchart step animation options
• bc18724 Additional fix since one flowchart diagram failed with crossing edges
• 7eec083 fix(elk): keep an edge reversed into a subgraph from crossing the edges into it
• 370c4af Merge pull request #8633 from mermaid-js/chore/remove-uuid
• 74e5ee8 Merge branch 'develop' into chore/remove-uuid
• 6e588f8 Merge pull request #8642 from mermaid-js/chore/e2e-speedup
• b6933f0 ci(e2e): speed up Playwright runs
• Additional commits viewable in compare view

Updates playwright from 1.64.1 to 1.65.0

Release notes

Sourced from playwright's releases.

v1.65.0

🥟 Run tests with Bun

The test runner now runs under Bun. Bun transpiles your TypeScript test files itself, so Playwright does not use Babel or its compilation cache. Pass the --bun flag, because without it bunx playwright test runs on Node.js:

bunx --bun playwright test

Our CI runs the test runner tests under Bun 1.4.3 on Linux. Some features work differently under Bun:

• There is no watch mode. UI mode does not run tests again when files change, and --only-changed does not follow imports.
• Bun loads modules itself, so --tsconfig and the JSX options in tsconfig.json have no effect, and custom ESM loaders are not supported.
• Stack traces do not include async frames, and API names do not include the class name: click instead of locator.click. This changes some step locations, step titles and error messages.
• Console output of a test does not get into the trace and UI mode.

🚨 Reports with only failures

New failures reporter prints failures and successful retries as they occur, followed by a summary, without progress output.

New onlyFailures option of the HTML, JSON and JUnit reporters keeps only tests with unexpected outcomes, flaky tests and interrupted tests:

// playwright.config.ts
import { defineConfig } from '@playwright/test';
export default defineConfig({
reporter: [
['failures'],
['html', { onlyFailures: true }],
],
});

🎯 Test runner

• New built-in -exclusive- test lock runs a test only when no other tests are running. All other tests continue to run in parallel with each other:

  test('restart the server', { lock: '-exclusive-' }, async () => {
    // No other test runs while this one is running.
  });

• test.skip(), test.fixme(), test.fail() and test.slow() now accept only a description. It is recorded in the test annotation:

  test('upload a file', async ({ page }) => {
    test.skip('Not implemented yet');
  });

... (truncated)

Commits

• a1f35e1 chore: mark v1.65.0 (#43925)
• a99c1ab cherry-pick(#43918): Revert "fix(docker): use latest stable Chrome for Testin...
• 6f9a7f5 cherry-pick(#43914): docs(release-notes): update Chromium version for 1.65
• daf93bb cherry-pick(#43912): feat(chromium): roll to r1254
• 6545e89 cherry-pick(#43902): chore(deps): bump runtime deps
• 0347448 fix(test runner): track shared ESM dependencies for only-changed (#43837)
• 86e6924 fix(clock): cancel real-time timer when replay ends paused (#43873)
• d745ae0 fix(route): wait for all active handlers before disabling interception (#43889)
• 6e3f5ff docs: release notes for v1.65 (#43874)
• aa33d27 fix(chromium): honor Linux config directories for channel connections (#43884)
• Additional commits viewable in compare view

Updates tailwindcss from 4.3.4 to 4.3.5

Release notes

Sourced from tailwindcss's releases.

v4.3.5

Fixed

• Canonicalization: improve performance in projects with many functional variant values (e.g. a matchVariant plugin with thousands of values) (#20663)
• Don't crash or create a fallback with the wrong color for a color-mix(…) without a color interpolation method (e.g. color-mix(var(--color-red-500)) or color-mix(currentcolor 50%, transparent)) (#20658, #20666)
• Ensure @tailwindcss/oxide-wasm32-wasi loads instead of hanging forever (e.g. with NAPI_RS_FORCE_WASI=error or in WebContainers) (#20667)
• Remove as: '*.css' from the @tailwindcss/turbopack setup in its README, because it breaks CSS modules (#20660)
• Ignore <!-- and --> between top-level rules in CSS instead of throwing or swallowing the next rule (e.g. a { color: red } --> b { color: blue }) (#20665)
• Ensure @tailwindcss/oxide-wasm32-wasi detects changed and new source files after the first scan (e.g. in WebContainers) (#20487)
• Prevent type errors with skipLibCheck: false caused by imports of unshipped modules in the @tailwindcss/node type declarations (#20632)

Changelog

Sourced from tailwindcss's changelog.

[4.3.5] - 2026-11-06

Fixed

• Canonicalization: improve performance in projects with many functional variant values (e.g. a matchVariant plugin with thousands ...

  Description has been truncated