Skip to content

👷 Update all non-major dependencies - #5284

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/all-minor-patch
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/all-minor-patch

Conversation

@renovate

@renovate renovate Bot commented Nov 14, 2026 •

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update Pending
@angular/common (source) 22.2.4 → 22.2.5 age adoption passing confidence devDependencies patch 22.2.6
@angular/compiler (source) 22.2.4 → 22.2.5 age adoption passing confidence devDependencies patch 22.2.6
@angular/core (source) 22.2.4 → 22.2.5 age adoption passing confidence devDependencies patch 22.2.6
@angular/platform-browser (source) 22.2.4 → 22.2.5 age adoption passing confidence devDependencies patch 22.2.6
@angular/router (source) 22.2.4 → 22.2.5 age adoption passing confidence devDependencies patch 22.2.6
@datadog/webpack-plugin (source) 3.4.0 → 3.5.0 age adoption passing confidence devDependencies minor 3.5.1
@mantine/core (source) 9.7.4 → 9.8.0 age adoption passing confidence dependencies minor 9.8.1
@mantine/hooks (source) 9.7.4 → 9.8.0 age adoption passing confidence dependencies minor 9.8.1
@module-federation/enhanced (source) 2.9.2 → 2.9.3 age adoption passing confidence devDependencies patch
@salesforce/cli (source) 2.157.7 → 2.158.7 age adoption passing confidence devDependencies minor
@swc/core (source) 1.16.21 → 1.16.22 age adoption passing confidence devDependencies patch
@tabler/icons-react (source) 3.50.0 → 3.51.0 age adoption passing confidence dependencies minor 3.52.0
@typescript-eslint/utils (source) 8.72.1 → 8.72.2 age adoption passing confidence devDependencies patch 8.73.0
@vitejs/plugin-react (source) 6.1.2 → 6.3.0 age adoption passing confidence devDependencies minor
@vitest/browser (source) 4.1.10 → 4.1.12 age adoption passing confidence devDependencies patch
@vitest/browser-playwright (source) 4.1.8 → 4.1.12 age adoption passing confidence devDependencies patch
@vitest/browser-webdriverio (source) 4.1.8 → 4.1.12 age adoption passing confidence devDependencies patch
@vitest/coverage-istanbul (source) 4.1.8 → 4.1.12 age adoption passing confidence devDependencies patch
@vitest/ui (source) 4.1.8 → 4.1.12 age adoption passing confidence devDependencies patch
@vue/compiler-dom (source) 3.5.44 → 3.5.45 age adoption passing confidence devDependencies patch
eslint-plugin-import-x 4.17.1 → 4.18.1 age adoption passing confidence devDependencies minor
eslint-plugin-jsdoc 65.4.2 → 65.4.5 age adoption passing confidence devDependencies patch 65.4.12 (+6)
github/codeql-action v4.39.1 → v4.39.3 age adoption passing confidence action patch
minimatch 11.0.3 → 11.0.8 age adoption passing confidence devDependencies patch 11.0.9
node (source) 26.12.1 → 26.13.1 age adoption passing confidence volta minor
node (source) 26.12.1-bookworm-slim → 26.13.0-bookworm-slim age adoption passing confidence stage minor 26.13.1-bookworm-slim
prettier (source) 3.9.10 → 3.10.0 age adoption passing confidence devDependencies minor 3.10.1
puppeteer (source) 25.16.0 → 25.17.0 age adoption passing confidence devDependencies minor 25.18.1 (+1)
rolldown (source) 1.2.16 → 1.3.2 age adoption passing confidence resolutions minor 1.3.3
tsdown (source) 0.23.4 → 0.23.7 age adoption passing confidence devDependencies patch
typescript-eslint (source) 8.72.1 → 8.72.2 age adoption passing confidence devDependencies patch 8.73.0
undici (source) 8.12.3 → 8.12.4 age adoption passing confidence devDependencies patch
vite (source) 8.3.5 → 8.3.8 age adoption passing confidence devDependencies patch
vue (source) 3.5.44 → 3.5.45 age adoption passing confidence dependencies patch
vue (source) 3.5.44 → 3.5.45 age adoption passing confidence devDependencies patch
vue-router (source) 5.4.0 → 5.5.0 age adoption passing confidence dependencies minor 5.5.1
vue-router (source) 5.4.0 → 5.5.0 age adoption passing confidence devDependencies minor 5.5.1
webdriverio (source) 9.27.2 → 9.33.1 age adoption passing confidence devDependencies minor
ws 8.22.1 → 8.22.2 age adoption passing confidence devDependencies patch 8.23.0

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

angular/angular (@​angular/common)

v22.2.5

Compare Source

core
Commit Type Description
6f06af76c9 fix add debugName option to rxResource
8c426b6cbc fix escape comment markers which share characters
ca3afffbdc fix remove attribute when img/video attr.src is null or undefined
forms
Commit Type Description
545eb3d07b fix reflect required validators in compat fields
a7b0e8ef9d fix support updateOn blur and submit for custom FormValueControl
96b027ebf6 perf avoid creating unused field injectors
router
Commit Type Description
ca42fefa56 fix read focusReset from the navigation extras
585271376a perf run loadComponent and loadChildren in root environment injector (g3-only)
DataDog/build-plugins (@​datadog/webpack-plugin)

v3.5.0

Compare Source

What's Changed

New Contributors

Full Changelog: DataDog/build-plugins@v3.4.0...v3.5.0

mantinedev/mantine (@​mantine/core)

v9.8.0: 🤭

Compare Source

View changelog with demos on mantine.dev website

Support Mantine development

You can now sponsor Mantine development with OpenCollective.
All funds are used to improve Mantine and create new features and components.

@​mantine/emoji package

New @mantine/emoji package provides emoji picker components. It works with any emoji
data source through adapters, emoji-mart
and emojibase-data adapters are included.

EmojiPicker

EmojiPicker displays a searchable emoji grid with category navigation,
skin tone selector, and emoji preview.

import data from '@emoji-mart/data';
import { emojiMartAdapter, EmojiPicker } from '@mantine/emoji';

const emojiData = emojiMartAdapter(data);

function Demo() {
  return (
    <EmojiPicker
      data={emojiData}
      onEmojiSelect={(emoji) => console.log(emoji)}
    />
  );
}
EmojiPickerInput

EmojiPickerInput is an input with an emoji picker dropdown.
It supports all standard input features like labels, descriptions, error messages, and sizes.

import data from '@emoji-mart/data';
import { emojiMartAdapter, EmojiPickerInput } from '@mantine/emoji';

const emojiData = emojiMartAdapter(data);

function Demo() {
  return <EmojiPickerInput data={emojiData} variant="default" size="sm" radius="md" label="Input label" withAsterisk={false} description="Input description" error="" placeholder="Select emoji" />;
}
EmojiPickerPopover

EmojiPickerPopover renders an emoji picker inside a popover dropdown.
Use it to build custom emoji picker triggers.

import { useState } from 'react';
import { ActionIcon } from '@mantine/core';
import data from '@emoji-mart/data';
import { emojiMartAdapter, EmojiPickerPopover } from '@mantine/emoji';

const emojiData = emojiMartAdapter(data);

function Demo() {
  const [emoji, setEmoji] = useState<string | null>(null);

  return (
    <EmojiPickerPopover
      data={emojiData}
      onEmojiSelect={(e) => setEmoji(e.emoji)}
    >
      <ActionIcon variant="default" size="lg">
        {emoji || '☺'}
      </ActionIcon>
    </EmojiPickerPopover>
  );
}
Diff component

New Diff component highlights differences between two strings.
It supports unified and split (side-by-side) display modes, configurable diff
granularity (characters, words, or lines), and context line collapsing.

// Demo.tsx
import { Diff } from '@mantine/code-highlight';
import { currentCode, previousCode } from './data';

function Demo() {
  return <Diff previousValue={previousCode} currentValue={currentCode} />;
}

// data.ts
export const previousCode = \`import { useState } from 'react';

function Counter() {
  const [count, setCount] = useState(0);
  return (
    <button onClick={() => setCount(count + 1)}>
      Count: {count}
    </button>
  );
}\
PhoneInput component

New PhoneInput component provides an international phone number input
with country selector, auto-detection, and formatting masks.

import { PhoneInput } from '@mantine/core';

function Demo() {
  return (
    <PhoneInput
      label="Phone number"
      placeholder="Your phone number"
      defaultCountry="us"
      renderFlag={(country) => (
        <img
          src={`https://hatscripts.github.io/circle-flags/flags/${country?.iso2 ?? 'xx'}.svg`}
          alt={country?.name ?? 'Select country'}
          style={{ width: 20, height: 20, borderRadius: 20 }}
        />
      )}
    />
  );
}
MaskedDateInput component

New MaskedDateInput component provides a date input with
individual masked fields for day, month, and year. It supports configurable field order,
custom separators, optional time fields, and a calendar dropdown for date selection.

import { MaskedDateInput } from '@mantine/dates';

function Demo() {
  return <MaskedDateInput label="Date of birth" />;
}
QuarterPicker and QuarterPickerInput components

New QuarterPicker and QuarterPickerInput components
allow picking quarters, multiple quarters and quarters ranges. They work the same way as MonthPicker
and MonthPickerInput; the value is the first day of the selected quarter in YYYY-MM-DD format.


WeekPicker and WeekPickerInput components

New WeekPicker and WeekPickerInput components
allow picking weeks, multiple weeks and weeks ranges. Clicking any day selects the whole week,
the value is the first day of the week according to firstDayOfWeek in YYYY-MM-DD format.


use-active-element hook

New use-active-element hook tracks the element that currently has focus.
Use it to build focus-aware UI or to disable global keyboard shortcuts while the user is typing:

import { Code, Group, Text, Textarea, TextInput } from '@mantine/core';
import { useActiveElement } from '@mantine/hooks';

function describe(element: Element | null) {
  if (!element) {
    return 'null';
  }

  return element.id ? `${element.tagName.toLowerCase()}#${element.id}` : element.tagName.toLowerCase();
}

function Demo() {
  const activeElement = useActiveElement();

  return (
    <>
      <Text>
        Focused element: <Code>{describe(activeElement)}</Code>
      </Text>

      <Group grow mt="md">
        <TextInput id="first-name" label="First name" placeholder="First name" />
        <TextInput id="last-name" label="Last name" placeholder="Last name" />
      </Group>

      <Textarea id="message" mt="md" label="Message" placeholder="Your message" />
    </>
  );
}
use-browser-language hook

New use-browser-language hook returns the browser language and
updates when the user changes it. Use it to pick a default locale for formatting or translations:

import { Code, Text } from '@mantine/core';
import { useBrowserLanguage } from '@mantine/hooks';

function Demo() {
  const language = useBrowserLanguage();

  return (
    <Text>
      Your browser language: <Code>{language ?? 'unknown'}</Code>
    </Text>
  );
}
Mentions component

New Mentions component is a textarea that opens a suggestions dropdown when
the user types @ or any other trigger. Picked mentions are stored in the value as @[Display](id)
markup, the user sees only the display text:

import { useState } from 'react';
import { Mentions } from '@mantine/core';

const users = [
  { id: 'walter', display: 'Walter White' },
  { id: 'jesse', display: 'Jesse Pinkman' },
  { id: 'saul', display: 'Saul Goodman' },
  { id: 'gus', display: 'Gustavo Fring' },
];

function Demo() {
  const [value, setValue] = useState('Hey @[Walter White](walter), are you ready?');

  return (
    <Mentions
      label="Comment"
      placeholder="Type @ to mention someone"
      value={value}
      onChange={(payload) => setValue(payload.value)}
      minRows={3}
    >
      <Mentions.Mention trigger="@" data={users} />
    </Mentions>
  );
}
Other changes
  • DayView and WeekView support slotLabelInterval prop to display time labels more often than once per hour
  • DayView and WeekView businessHours prop accepts exact minutes, business hours colors can be changed with CSS variables
  • MobileMonthView supports withWeekendDays prop to hide weekend days
  • ScrollArea supports --scrollarea-offset-size CSS variable to change the gap reserved by offsetScrollbars
  • Popover and components based on it support clickOutsideCapture prop to close the dropdown when the click target stops event propagation
  • getUploadImageExtension in @​mantine/tiptap uploads images embedded in pasted HTML, use shouldUploadPastedImage option to control which images are uploaded
  • Keyboard navigation in DatePicker and other @mantine/dates pickers has been improved: arrow keys move focus across months and focus returns to the input when the dropdown closes
  • @mantine/form exports UseContextForm type
  • Notifications support autoCloseProgressPosition prop to display the auto close progress line at the top of the notification

v9.7.5

Compare Source

  • [@mantine/tiptap] Keep aria-pressed on toggle controls in both states (#​9376)
  • [@mantine/core] Indicator: Respect reduced motion in the processing animation (#​9375)
  • [@mantine/schedule] YearView: Fix multi-day events not showing when they start in the previous year (#​9374)
  • [@mantine/dates] Use dayjs to create years in YearsList and CalendarHeader (#​9372)
  • [@mantine/core] NumberInput: Fix inputMode prop being overridden (#​9371)
  • [@mantine/core] Tour: Add position="center" to Tour.Step to place the tooltip over the target (#​9369)
  • [@mantine/charts] BarChart: Fix waterfall type mutating the data prop (#​9365)
  • [@mantine/hooks] use-mask: Fix autofill keydown errors (#​9362)
  • [@mantine/core] Combobox: Fix hidden input dropping falsy values (#​9359)
  • [@mantine/core] Popover: Fix preventPositionChangeWhenVisible not locking dropdown side on open (#​9358)
  • [@mantine/hooks] use-move: End scrubbing when touch is canceled (#​9354)
  • [@mantine/hooks] use-focus-within: Keep focus within SVG descendants (#​9353)
  • [@mantine/hooks] use-window-event: Update event listener options (#​9352)
  • [@mantine/hooks] use-scroller: Track delayed and replaced containers (#​9351)
  • [@mantine/hooks] use-resize-observer: Prevent render loops with inline options (#​9350)
  • [@mantine/hooks] use-long-press: Prevent duplicate timers on overlapping presses (#​9349)
  • [@mantine/hooks] use-input-state: Fix setter type to accept callbacks (#​9347)
  • [@mantine/mcp-server] get_api: Resolve symbols documented in guide pages (#​9341) (#​9346)
  • [@mantine/core] Cascader: Fix keyboard navigation not being ignored during IME composition (#​9343)
  • [@mantine/core] MultiSelect, TreeSelect: Fix Backspace removing the last value during IME composition (#​9340)
  • [@mantine/hooks] use-scroll-into-view: Clamp animation progress before easing (#​9338)
  • [@mantine/hooks] use-timeout: Fix callback restarts and error recovery (#​9336)
  • [@mantine/schedule] MonthView: Fix ArrowLeft and ArrowRight not being mirrored in RTL (#​9335)
  • [@mantine/core] TreeSelect: Fix ArrowLeft and ArrowRight not being mirrored in RTL (#​9334)
  • [@mantine/core] Fix leading decimal values being treated as theme sizes (#​9333)
  • [@mantine/core] Menu: Keep explicit aria-disabled on items and Menubar targets (#​9332)
  • [@mantine/dates] Calendar: Fix ArrowLeft and ArrowRight not being mirrored in RTL (#​9330)
  • [@mantine/hooks] use-hash: Keep setter state consistent with the URL (#​9328)
  • [@mantine/core] Parse four-digit hex colors in color functions (#​9327)
  • [@mantine/schedule] Add eventTimeFormat prop support to AgendaView, MobileMonthView, DayView, WeekView, MonthView and Schedule components (#​9356)
  • [@mantine/core] Add loaderProps support to all input components
module-federation/core (@​module-federation/enhanced)

v2.9.3

Compare Source

Patch Changes
  • ee32a0d: Keep one consume-shared module per requiredVersion range. Two packages that
    require different ranges of the same shared dependency no longer collapse into
    one module, so each gets its own version check.
  • caafd8d: Read the version for include.version and exclude.version on consumed
    shared modules from the package.json whose name matches the consumed
    package. Prefix consumes such as 'lib/' matched against lib/sub, scoped
    packages, and node_modules suffix matches previously skipped the filter
    and were always consumed. Relative, absolute, and aliased consume configs
    are unchanged unless packageName is set.
  • edf1219: HoistContainerReferencesPlugin no longer hoists modules that webpack already pruned. The module graph walk now skips connections whose active state is false, such as an unused import of a sideEffects: false package, so the runtime chunk keeps only modules that are reachable through an active connection.
  • b4b5477: Give each shared tree-shaking child compiler its own filesystem cache pack and close it after its run. Before, the children overwrote the parent's cache pack, so the next build rebuilt every parent module.
  • 543eba3: Test include.request and exclude.request on provided shared modules only against the import request, or against the path after node_modules/ (for example lodash/get.js) when allowNodeModulesSuffixMatch matches, never against the resolved file path. A prefix such as 'lodash/' with include: { request: 'get' } and a direct entry such as react with include: { request: 'react' } now provide their modules, and an exclude.request pattern no longer drops modules whose absolute path happens to match it.
  • [fdaeb75](https://redirect.git

[!IMPORTANT]
✂ PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "every weekend"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

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

@renovate
renovate Bot requested a review from a team as a code owner November 14, 2026 07:06
@renovate renovate Bot added the dependencies Pull requests that update a dependency file label Nov 14, 2026
@datadog-prod-us1-4

datadog-prod-us1-4 Bot commented Nov 14, 2026 •

Copy link
Copy Markdown

Pipelines  Tests

❌ Errors

Your PR has failed checks. Please review the issues below and take necessary action before merging.

🚦 2 Pipeline jobs failed

DataDog/browser-sdk | e2e: [chromium] — ❌ 3 tests failed

View more details · View in GitLab

❌ developer extension › should switch between tabs › async from developer-extension/developerExtension.scenario.ts
Test timeout of 30000ms exceeded.

[chromium] › developer-extension/developerExtension.scenario.ts:8:13 › developer extension › should switch between tabs › async 

    Test timeout of 30000ms exceeded.

    Error: page.evaluate: Target page, context or browser has been closed

       at ../lib/framework/waitForRequests.ts:15

...
❌ developer extension › should switch between tabs › bundle from developer-extension/developerExtension.scenario.ts
Test timeout of 30000ms exceeded.

[chromium] › developer-extension/developerExtension.scenario.ts:8:13 › developer extension › should switch between tabs › bundle 

    Test timeout of 30000ms exceeded.

    Error: page.evaluate: Target page, context or browser has been closed

       at ../lib/framework/waitForRequests.ts:15

...
↳ and 1 more — View all
DataDog/browser-sdk | check-node-version

View more details · View in GitLab

ℹ️ Info

No other issues found (see more)

❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 78.13% (+0.01%)

Useful? React with 👍 / 👎

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: af5736b | Docs | View more details | Give us feedback!

@datadog-prod-us1-4 datadog-prod-us1-4 Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bits Code Review: PASS

More details

The updated browser-test dependencies worked in a focused Chromium run with and without Istanbul coverage. Compatibility across the full test suite and the updated Node image remains unverified.

Was this helpful? React 👍 or 👎

Open Bits AI session

🤖 Bits Code Review · Commit ce0587d

@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from ce0587d to 0a1a041 Compare November 15, 2026 16:46
@cit-pr-commenter-54b7da

cit-pr-commenter-54b7da Bot commented Nov 15, 2026 •

Copy link
Copy Markdown

Bundles Sizes Evolution

📦 Bundle Name Base Size Local Size 𝚫 𝚫% Status
Rum Salesforce 192.50 KiB 192.50 KiB 0 B 0.00% ✅
Rum 192.48 KiB 192.48 KiB 0 B 0.00% ✅
Rum Salesforce Profiler 8.01 KiB 8.01 KiB 0 B 0.00% ✅
Rum Profiler 8.01 KiB 8.01 KiB 0 B 0.00% ✅
Rum Salesforce Recorder 32.62 KiB 32.62 KiB 0 B 0.00% ✅
Rum Recorder 32.62 KiB 32.62 KiB 0 B 0.00% ✅
Logs 60.28 KiB 60.28 KiB 0 B 0.00% ✅
Rum Slim 148.42 KiB 148.42 KiB 0 B 0.00% ✅
Worker 24.23 KiB 24.23 KiB 0 B 0.00% ✅
Rum Shopify 223.54 KiB 223.54 KiB 0 B 0.00% ✅
Rum Shopify Profiler 8.00 KiB 8.00 KiB 0 B 0.00% ✅
Rum Shopify Recorder 4.85 KiB 4.85 KiB 0 B 0.00% ✅

@datadog-prod-us1-4 datadog-prod-us1-4 Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bits Code Review: WARN

The Vitest integrations require 4.1.12 while the runner remains at 4.1.8, producing an unsupported mixed-version warning. Browser execution was blocked by a missing Chromium binary, leaving the runtime impact unconfirmed.

Open Bits AI session

🤖 Bits Code Review · Commit 0a1a041

Comment thread package.json
"@vitest/coverage-istanbul": "4.1.8",
"@vitest/ui": "4.1.8",
"@vitest/browser": "4.1.12",
"@vitest/browser-playwright": "4.1.12",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Upgrade the Vitest runner alongside its integrations

The upgraded Playwright and coverage integrations require vitest@4.1.12, while the runner remains pinned to 4.1.8. The active unit-test command emits “Running mixed versions is not supported,” and CI enables the mismatched Istanbul provider too. This introduces a compatibility risk in the test toolchain, although a runtime regression was not established. Upgrade vitest alongside these integrations and regenerate yarn.lock.

React: 👍 useful · 👎 wrong · 😕 unclear · 👀 right, but not acting on it

What each reaction means
  • 👍 Useful: correct, and you're fixing it or will.
  • 👎 Wrong: the finding is incorrect, for example the bug can't happen or the code was misread.
  • 😕 Unclear: you can't tell what it means or why it matters.
  • 👀 Right, not acting: correct, but intended, out of scope for this PR, a known risk, or too minor.

🤖 Bits Code Review · Open Bits AI session

@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from 0a1a041 to ec54660 Compare November 16, 2026 02:24

@datadog-prod-us1-4 datadog-prod-us1-4 Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bits Code Review: WARN

The upgraded Vitest companion packages require 4.1.12, while the runner remains at 4.1.8 and emits unsupported mixed-version warnings. A functional regression remains unproven.

Open Bits AI session

🤖 Bits Code Review · Commit ec54660

Comment thread package.json
"@vitest/coverage-istanbul": "4.1.8",
"@vitest/ui": "4.1.8",
"@vitest/browser": "4.1.12",
"@vitest/browser-playwright": "4.1.12",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Align the Vitest runner with its upgraded companion packages

The runner remains at vitest@4.1.8, while the upgraded Playwright provider, Istanbul coverage provider, and UI require exactly 4.1.12. This introduces conflicting peer requirements into the normal unit-test configuration, including CI coverage. A focused invocation emitted unsupported mixed-version warnings, but functional failure remains unproven. Upgrade the runner to 4.1.12 and regenerate yarn.lock alongside these updates.

React: 👍 useful · 👎 wrong · 😕 unclear · 👀 right, but not acting on it

What each reaction means
  • 👍 Useful: correct, and you're fixing it or will.
  • 👎 Wrong: the finding is incorrect, for example the bug can't happen or the code was misread.
  • 😕 Unclear: you can't tell what it means or why it matters.
  • 👀 Right, not acting: correct, but intended, out of scope for this PR, a known risk, or too minor.

🤖 Bits Code Review · Open Bits AI session

@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from ec54660 to c2cde58 Compare November 16, 2026 07:09

@datadog-prod-us1-4 datadog-prod-us1-4 Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bits Code Review: WARN

Vitest's upgraded providers require 4.1.12 while the runner remains at 4.1.8, triggering an unsupported-version warning during coverage initialization. An actual test or coverage failure was not established.

Open Bits AI session

🤖 Bits Code Review · Commit c2cde58

Comment thread package.json
"@vitest/browser": "4.1.12",
"@vitest/browser-playwright": "4.1.12",
"@vitest/browser-webdriverio": "4.1.12",
"@vitest/coverage-istanbul": "4.1.12",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Align the Vitest runner with its upgraded providers

The upgraded Playwright and Istanbul packages require vitest@4.1.12, but the runner remains pinned to 4.1.8. The unit-test configuration loads these packages and enables Istanbul in CI, introducing an unsupported dependency combination that emits Vitest's mixed-version warning. Browser-test or coverage incompatibilities remain possible, although no failing test was demonstrated. Update the runner alongside these packages and regenerate yarn.lock.

React: 👍 useful · 👎 wrong · 😕 unclear · 👀 right, but not acting on it

What each reaction means
  • 👍 Useful: correct, and you're fixing it or will.
  • 👎 Wrong: the finding is incorrect, for example the bug can't happen or the code was misread.
  • 😕 Unclear: you can't tell what it means or why it matters.
  • 👀 Right, not acting: correct, but intended, out of scope for this PR, a known risk, or too minor.

🤖 Bits Code Review · Open Bits AI session

@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from c2cde58 to 076ecc3 Compare November 16, 2026 08:06

@datadog-prod-us1-4 datadog-prod-us1-4 Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bits Code Review: PASS

More details

The reported Vitest readiness exception is caught by the browser client, and focused browser execution completed successfully with the upgraded provider and unchanged runner.

Was this helpful? React 👍 or 👎

Open Bits AI session

🤖 Bits Code Review · Commit 076ecc3

@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from 076ecc3 to 4ab8c48 Compare November 16, 2026 11:01

@datadog-prod-us1-4 datadog-prod-us1-4 Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bits Code Review: WARN

The upgraded Vitest companions require runner 4.1.12, but the runner remains at 4.1.8, creating an explicitly unsupported combination. Browser initialization succeeds; an actual test or coverage failure remains unproven.

Open Bits AI session

🤖 Bits Code Review · Commit 4ab8c48

Comment thread package.json
"@vitest/browser": "4.1.12",
"@vitest/browser-playwright": "4.1.12",
"@vitest/browser-webdriverio": "4.1.12",
"@vitest/coverage-istanbul": "4.1.12",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Align the Vitest runner with its upgraded companions

Browser unit tests and CI coverage now load the Playwright and Istanbul companions at 4.1.12 while vitest remains pinned to 4.1.8. Both companions require exactly vitest 4.1.12, and Vitest explicitly warns that mixed versions are unsupported. Initialization succeeds, so a test or coverage failure is not established, but the active test toolchain violates its compatibility requirements. Upgrade vitest alongside its companions and regenerate yarn.lock.

React: 👍 useful · 👎 wrong · 😕 unclear · 👀 right, but not acting on it

What each reaction means
  • 👍 Useful: correct, and you're fixing it or will.
  • 👎 Wrong: the finding is incorrect, for example the bug can't happen or the code was misread.
  • 😕 Unclear: you can't tell what it means or why it matters.
  • 👀 Right, not acting: correct, but intended, out of scope for this PR, a known risk, or too minor.

🤖 Bits Code Review · Open Bits AI session

@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from 4ab8c48 to 9a6ffdd Compare November 16, 2026 14:18

@datadog-prod-us1-4 datadog-prod-us1-4 Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bits Code Review: FAIL

The Node upgrade leaves CI selecting its older image, causing the version guard to reject the new pins. The Vitest update also leaves the runner and providers with conflicting exact-version requirements.

Open Bits AI session

🤖 Bits Code Review · Commit 9a6ffdd

Comment thread Dockerfile
RUN npx -y playwright@1.40.1 install --with-deps chromium firefox webkit

FROM node:26.12.1-bookworm-slim
FROM node:26.13.0-bookworm-slim

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Rebuild and select the CI image for the Node upgrade

CI still selects image 135, introduced with Node 26.12.1, while this change requires 26.13.0 in both Docker and Volta. Because the image-build job is manual, the normal pipeline continues using the older runtime and scripts/check-node-version.ts exits 1, blocking CI. Bump CURRENT_CI_IMAGE in .gitlab-ci.yml and build the corresponding image alongside this upgrade.

React: 👍 useful · 👎 wrong · 😕 unclear · 👀 right, but not acting on it

What each reaction means
  • 👍 Useful: correct, and you're fixing it or will.
  • 👎 Wrong: the finding is incorrect, for example the bug can't happen or the code was misread.
  • 😕 Unclear: you can't tell what it means or why it matters.
  • 👀 Right, not acting: correct, but intended, out of scope for this PR, a known risk, or too minor.

🤖 Bits Code Review · Open Bits AI session

Comment thread package.json
"@vitest/coverage-istanbul": "4.1.8",
"@vitest/ui": "4.1.8",
"@vitest/browser": "4.1.12",
"@vitest/browser-playwright": "4.1.12",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Upgrade the Vitest runner with its providers

The Vitest runner remains at 4.1.8, while the upgraded Playwright and Istanbul providers require exactly 4.1.12; the runner reciprocally requires 4.1.8 providers. CI unit tests enable both providers, introducing an explicitly unsupported mixed-version configuration. Runtime failure is unproven, but the active test toolchain now violates its compatibility requirements. Upgrade vitest to 4.1.12 and regenerate yarn.lock.

React: 👍 useful · 👎 wrong · 😕 unclear · 👀 right, but not acting on it

What each reaction means
  • 👍 Useful: correct, and you're fixing it or will.
  • 👎 Wrong: the finding is incorrect, for example the bug can't happen or the code was misread.
  • 😕 Unclear: you can't tell what it means or why it matters.
  • 👀 Right, not acting: correct, but intended, out of scope for this PR, a known risk, or too minor.

🤖 Bits Code Review · Open Bits AI session

@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from 9a6ffdd to bd1daff Compare November 16, 2026 15:37

@datadog-prod-us1-4 datadog-prod-us1-4 Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bits Code Review: WARN

Vitest’s browser and coverage plugins move to 4.1.12 while the runner stays at 4.1.8, violating their exact peer requirements. The active test configuration uses these plugins, but a runtime failure has not been established.

Open Bits AI session

🤖 Bits Code Review · Commit bd1daff

Comment thread package.json
"@vitest/coverage-istanbul": "4.1.8",
"@vitest/ui": "4.1.8",
"@vitest/browser": "4.1.12",
"@vitest/browser-playwright": "4.1.12",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Align the Vitest runner with its upgraded plugins

The upgraded Playwright and Istanbul plugins require exactly vitest@4.1.12, but the runner remains at 4.1.8. Yarn confirms the unsatisfied peer requirements. The active unit-test configuration uses Playwright and enables Istanbul coverage in CI, so these paths now use an unsupported version combination with potential execution or coverage failures. Runtime failure was not established. Update the runner alongside its plugins and regenerate yarn.lock.

React: 👍 useful · 👎 wrong · 😕 unclear · 👀 right, but not acting on it

What each reaction means
  • 👍 Useful: correct, and you're fixing it or will.
  • 👎 Wrong: the finding is incorrect, for example the bug can't happen or the code was misread.
  • 😕 Unclear: you can't tell what it means or why it matters.
  • 👀 Right, not acting: correct, but intended, out of scope for this PR, a known risk, or too minor.

🤖 Bits Code Review · Open Bits AI session

@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from bd1daff to 6feda11 Compare November 16, 2026 16:50

@datadog-prod-us1-4 datadog-prod-us1-4 Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bits Code Review: WARN

Vitest’s configured browser and coverage providers move to 4.1.12 while the runner stays at 4.1.8, violating their exact peer requirements. A resulting runtime failure remains unproven.

Open Bits AI session

🤖 Bits Code Review · Commit 6feda11

Comment thread package.json
"@vitest/browser": "4.1.12",
"@vitest/browser-playwright": "4.1.12",
"@vitest/browser-webdriverio": "4.1.12",
"@vitest/coverage-istanbul": "4.1.12",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Keep the Vitest runner and its providers on matching versions

The Playwright and Istanbul providers now require vitest@4.1.12, while the runner remains pinned to 4.1.8 and requires those providers at 4.1.8. The unit-test configuration loads Playwright and enables Istanbul coverage in CI, so this update introduces unsupported combinations into the normal test stack. Vitest warns that mixed coverage versions may cause bugs; a runtime failure has not been established. Upgrade the runner and regenerate the lockfile together, or retain matching provider versions.

React: 👍 useful · 👎 wrong · 😕 unclear · 👀 right, but not acting on it

What each reaction means
  • 👍 Useful: correct, and you're fixing it or will.
  • 👎 Wrong: the finding is incorrect, for example the bug can't happen or the code was misread.
  • 😕 Unclear: you can't tell what it means or why it matters.
  • 👀 Right, not acting: correct, but intended, out of scope for this PR, a known risk, or too minor.

🤖 Bits Code Review · Open Bits AI session

@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from 6feda11 to 96bf2c9 Compare November 16, 2026 20:49

@datadog-prod-us1-4 datadog-prod-us1-4 Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bits Code Review: FAIL

Two independent version-alignment gaps were found: the CI image tag in .gitlab-ci.yml was not updated to match the Node 26.13.0 bump (causing a pipeline failure via check-node-version.ts), and the vitest package remains pinned to 4.1.8 while its Istanbul coverage provider was moved to 4.1.12, creating an unsupported peer-version combination in CI.

Open Bits AI session

🤖 Bits Code Review · Commit 96bf2c9

Comment thread package.json
"@vitest/browser": "4.1.12",
"@vitest/browser-playwright": "4.1.12",
"@vitest/browser-webdriverio": "4.1.12",
"@vitest/coverage-istanbul": "4.1.12",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Align Vitest core with the updated coverage provider

CI enables Istanbul coverage, but this update moves its provider to 4.1.12 while vitest remains pinned to 4.1.8. Both packages declare exact matching peer versions, and coverage initialization explicitly warns that mixed versions are unsupported. This introduces an unsupported combination into the existing CI test path, although an actual test failure was not demonstrated. Upgrade vitest to 4.1.12 and regenerate yarn.lock together.

React: 👍 useful · 👎 wrong · 😕 unclear · 👀 right, but not acting on it

What each reaction means
  • 👍 Useful: correct, and you're fixing it or will.
  • 👎 Wrong: the finding is incorrect, for example the bug can't happen or the code was misread.
  • 😕 Unclear: you can't tell what it means or why it matters.
  • 👀 Right, not acting: correct, but intended, out of scope for this PR, a known risk, or too minor.

🤖 Bits Code Review · Open Bits AI session

Comment thread Dockerfile
RUN npx -y playwright@1.40.1 install --with-deps chromium firefox webkit

FROM node:26.12.1-bookworm-slim
FROM node:26.13.0-bookworm-slim

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Update the CI image tag alongside the Node bump

Normal GitLab pipelines still select CURRENT_CI_IMAGE 135, introduced with Node 26.12.1. Updating Dockerfile and Volta to 26.13.0 does not update that runtime because the ci-image job is manual. Consequently, scripts/check-node-version.ts detects the mismatch and exits with status 1, failing the pipeline. Bump CURRENT_CI_IMAGE in .gitlab-ci.yml and build the corresponding image alongside this upgrade.

React: 👍 useful · 👎 wrong · 😕 unclear · 👀 right, but not acting on it

What each reaction means
  • 👍 Useful: correct, and you're fixing it or will.
  • 👎 Wrong: the finding is incorrect, for example the bug can't happen or the code was misread.
  • 😕 Unclear: you can't tell what it means or why it matters.
  • 👀 Right, not acting: correct, but intended, out of scope for this PR, a known risk, or too minor.

🤖 Bits Code Review · Open Bits AI session

@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from 96bf2c9 to c3cd73d Compare November 17, 2026 05:30

@datadog-prod-us1-4 datadog-prod-us1-4 Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bits Code Review: FAIL

The Volta Node pin (26.13.1) and the Docker image pin (26.13.0) are misaligned, which guarantees failure of the check-node-version CI job that requires exact equality between the two versions.

Open Bits AI session

🤖 Bits Code Review · Commit c3cd73d

Comment thread package.json
},
"volta": {
"node": "26.12.1",
"node": "26.13.1",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Keep the Volta and Docker Node versions aligned

Volta now pins Node 26.13.1 while Docker pins 26.13.0. The existing check-node-version CI job requires exact equality between Docker, Volta, and the runtime version, and exits with status 1 on mismatch. These conflicting pins therefore guarantee CI failure even after rebuilding the image. Align Volta with Docker's version.

Suggested change
"node": "26.13.1",
"node": "26.13.0",

React: 👍 useful · 👎 wrong · 😕 unclear · 👀 right, but not acting on it

What each reaction means
  • 👍 Useful: correct, and you're fixing it or will.
  • 👎 Wrong: the finding is incorrect, for example the bug can't happen or the code was misread.
  • 😕 Unclear: you can't tell what it means or why it matters.
  • 👀 Right, not acting: correct, but intended, out of scope for this PR, a known risk, or too minor.

🤖 Bits Code Review · Open Bits AI session

@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from c3cd73d to 94d6538 Compare November 17, 2026 23:23

@datadog-prod-us1-4 datadog-prod-us1-4 Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bits Code Review: WARN

The Vitest browser and coverage providers now require 4.1.12 while the runner remains pinned to 4.1.8. This creates an unsupported test configuration; an actual test failure was not established.

Open Bits AI session

🤖 Bits Code Review · Commit 94d6538

Comment thread package.json
"@vitest/ui": "4.1.8",
"@typescript-eslint/utils": "8.72.2",
"@vitest/browser": "4.1.12",
"@vitest/browser-playwright": "4.1.12",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Keep the Vitest runner aligned with its providers

The configured Playwright browser provider and Istanbul coverage provider now require exactly vitest@4.1.12, while the runner remains pinned to 4.1.8. These providers previously matched the runner. This introduces unsupported peer dependencies for local browser tests and CI coverage, with mixed-version startup warnings; a test failure has not been established. Upgrade the runner alongside its companions and regenerate yarn.lock.

React: 👍 useful · 👎 wrong · 😕 unclear · 👀 right, but not acting on it

What each reaction means
  • 👍 Useful: correct, and you're fixing it or will.
  • 👎 Wrong: the finding is incorrect, for example the bug can't happen or the code was misread.
  • 😕 Unclear: you can't tell what it means or why it matters.
  • 👀 Right, not acting: correct, but intended, out of scope for this PR, a known risk, or too minor.

🤖 Bits Code Review · Open Bits AI session

@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from 94d6538 to 00ab827 Compare November 18, 2026 02:14

@datadog-prod-us1-4 datadog-prod-us1-4 Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bits Code Review: WARN

Vitest’s upgraded companion packages require 4.1.12 while the runner remains at 4.1.8, producing unsupported-version warnings. Browser execution could not be validated because the sandbox lacks the required Chromium executable.

Open Bits AI session

🤖 Bits Code Review · Commit 00ab827

Comment thread package.json
"@vitest/browser": "4.1.12",
"@vitest/browser-playwright": "4.1.12",
"@vitest/browser-webdriverio": "4.1.12",
"@vitest/coverage-istanbul": "4.1.12",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Align Vitest runner with upgraded companion packages

The upgraded Playwright, Istanbul coverage, and UI packages require vitest@4.1.12, but the runner remains pinned to 4.1.8. The configured browser tests and CI coverage therefore use an unsupported combination; initialization confirms mixed-version warnings. Runtime breakage remains unproven, but the toolchain no longer satisfies its peer requirements. Upgrade the runner alongside its companions and regenerate yarn.lock.

React: 👍 useful · 👎 wrong · 😕 unclear · 👀 right, but not acting on it

What each reaction means
  • 👍 Useful: correct, and you're fixing it or will.
  • 👎 Wrong: the finding is incorrect, for example the bug can't happen or the code was misread.
  • 😕 Unclear: you can't tell what it means or why it matters.
  • 👀 Right, not acting: correct, but intended, out of scope for this PR, a known risk, or too minor.

🤖 Bits Code Review · Open Bits AI session

@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from 00ab827 to 44bca5a Compare November 18, 2026 05:58

@datadog-prod-us1-4 datadog-prod-us1-4 Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bits Code Review: FAIL

Docker and Volta pin different Node versions, making the existing CI consistency check impossible to satisfy. Vitest providers also require a newer runner than the one pinned.

Open Bits AI session

🤖 Bits Code Review · Commit 44bca5a

Comment thread package.json
},
"volta": {
"node": "26.12.1",
"node": "26.13.1",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Align the Volta and Docker Node versions

Docker pins Node 26.13.0 while Volta now pins 26.13.1. scripts/check-node-version.ts requires the Docker, Volta, and process versions to match exactly, so the check-node-version CI job necessarily fails, even after rebuilding the image. Align the pins.

Suggested change
"node": "26.13.1",
"node": "26.13.0",

React: 👍 useful · 👎 wrong · 😕 unclear · 👀 right, but not acting on it

What each reaction means
  • 👍 Useful: correct, and you're fixing it or will.
  • 👎 Wrong: the finding is incorrect, for example the bug can't happen or the code was misread.
  • 😕 Unclear: you can't tell what it means or why it matters.
  • 👀 Right, not acting: correct, but intended, out of scope for this PR, a known risk, or too minor.

🤖 Bits Code Review · Open Bits AI session

Comment thread package.json
"@vitest/ui": "4.1.8",
"@typescript-eslint/utils": "8.72.2",
"@vitest/browser": "4.1.12",
"@vitest/browser-playwright": "4.1.12",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Upgrade the Vitest runner with its providers

The updated Playwright and Istanbul providers require exactly vitest@4.1.12, but the runner remains at 4.1.8. The unit configuration uses Playwright and enables Istanbul in CI, introducing unsupported runner/provider combinations and a coverage version-mismatch warning. Functional breakage remains unverified; upgrade the runner with its companions and regenerate yarn.lock.

React: 👍 useful · 👎 wrong · 😕 unclear · 👀 right, but not acting on it

What each reaction means
  • 👍 Useful: correct, and you're fixing it or will.
  • 👎 Wrong: the finding is incorrect, for example the bug can't happen or the code was misread.
  • 😕 Unclear: you can't tell what it means or why it matters.
  • 👀 Right, not acting: correct, but intended, out of scope for this PR, a known risk, or too minor.

🤖 Bits Code Review · Open Bits AI session

@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from 44bca5a to 9345dcb Compare November 18, 2026 11:52

@datadog-prod-us1-4 datadog-prod-us1-4 Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bits Code Review: FAIL

The two most critical issues are a Node version mismatch between the Docker base image (26.13.0) and Volta pin (26.13.1) that is already breaking the check-node-version CI job, and a Vitest version mismatch where updated add-ons require 4.1.12 but the root workspace still provides 4.1.8, introducing unsatisfied peer dependencies.

Open Bits AI session

🤖 Bits Code Review · Commit 9345dcb

Comment thread Dockerfile
RUN npx -y playwright@1.40.1 install --with-deps chromium firefox webkit

FROM node:26.12.1-bookworm-slim
FROM node:26.13.0-bookworm-slim

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Align the Docker and Volta Node versions and rebuild the CI image

The GitLab check-node-version job requires the Docker base image, Volta pin, and running Node version to match exactly. Docker now pins 26.13.0 and Volta pins 26.13.1, so the job exits with an error on this revision and will still fail if the Docker image is rebuilt as-is. Use the same patch version in both files, then bump CURRENT_CI_IMAGE and build that tag so CI picks up the aligned version.

React: 👍 useful · 👎 wrong · 😕 unclear · 👀 right, but not acting on it

What each reaction means
  • 👍 Useful: correct, and you're fixing it or will.
  • 👎 Wrong: the finding is incorrect, for example the bug can't happen or the code was misread.
  • 😕 Unclear: you can't tell what it means or why it matters.
  • 👀 Right, not acting: correct, but intended, out of scope for this PR, a known risk, or too minor.

🤖 Bits Code Review · Open Bits AI session

Comment thread package.json
"@vitest/ui": "4.1.8",
"@typescript-eslint/utils": "8.72.2",
"@vitest/browser": "4.1.12",
"@vitest/browser-playwright": "4.1.12",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Upgrade the Vitest runner alongside its add-ons

The updated Playwright provider, Istanbul coverage provider, and UI add-on each declare an exact Vitest 4.1.12 peer, but the root workspace still provides 4.1.8. This introduces unsatisfied peer requirements on install and makes yarn test:unit load the Playwright provider with an unsupported runner version, even though the unit job passed on this revision. Upgrade the root runner to 4.1.12 and regenerate the lockfile.

React: 👍 useful · 👎 wrong · 😕 unclear · 👀 right, but not acting on it

What each reaction means
  • 👍 Useful: correct, and you're fixing it or will.
  • 👎 Wrong: the finding is incorrect, for example the bug can't happen or the code was misread.
  • 😕 Unclear: you can't tell what it means or why it matters.
  • 👀 Right, not acting: correct, but intended, out of scope for this PR, a known risk, or too minor.

🤖 Bits Code Review · Open Bits AI session

@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from 9345dcb to af5736b Compare November 18, 2026 13:49

@datadog-prod-us1-4 datadog-prod-us1-4 Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bits Code Review: FAIL

Two version-alignment problems are present: the vitest runner (4.1.8) is out of sync with its Playwright and Istanbul plugins (which require exactly 4.1.12), and the Docker Node pin (26.13.0) is out of sync with the Volta pin (26.13.1), causing the check-node-version CI job to unconditionally fail.

Open Bits AI session

🤖 Bits Code Review · Commit af5736b

Comment thread package.json
"@vitest/ui": "4.1.8",
"@typescript-eslint/utils": "8.72.2",
"@vitest/browser": "4.1.12",
"@vitest/browser-playwright": "4.1.12",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Upgrade the Vitest runner alongside its plugins

The upgraded Playwright provider and Istanbul coverage plugin both declare an exact Vitest 4.1.12 peer requirement, but the root still supplies 4.1.8. Yarn reports peer conflicts for the plugins used by browser unit tests and CI coverage, leaving those paths on an unsupported version pairing even though the unit job passed. Pin Vitest to 4.1.12 and regenerate the root lockfile.

React: 👍 useful · 👎 wrong · 😕 unclear · 👀 right, but not acting on it

What each reaction means
  • 👍 Useful: correct, and you're fixing it or will.
  • 👎 Wrong: the finding is incorrect, for example the bug can't happen or the code was misread.
  • 😕 Unclear: you can't tell what it means or why it matters.
  • 👀 Right, not acting: correct, but intended, out of scope for this PR, a known risk, or too minor.

🤖 Bits Code Review · Open Bits AI session

Comment thread package.json
},
"volta": {
"node": "26.12.1",
"node": "26.13.1",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Synchronize Docker and Volta Node versions

The check-node-version CI job requires the Dockerfile, Volta, and runtime Node versions to match exactly. Volta now pins 26.13.1 while Docker specifies 26.13.0, so the check exits with status 1 regardless of the runtime version, even after rebuilding the image. Align the pins and rebuild/select the matching CI image via CURRENT_CI_IMAGE.

React: 👍 useful · 👎 wrong · 😕 unclear · 👀 right, but not acting on it

What each reaction means
  • 👍 Useful: correct, and you're fixing it or will.
  • 👎 Wrong: the finding is incorrect, for example the bug can't happen or the code was misread.
  • 😕 Unclear: you can't tell what it means or why it matters.
  • 👀 Right, not acting: correct, but intended, out of scope for this PR, a known risk, or too minor.

🤖 Bits Code Review · Open Bits AI session

This branch has not been deployed

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

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants