fix(deps): update npm minor and patch dependencies#2139
fix(deps): update npm minor and patch dependencies#2139red-hat-konflux[bot] wants to merge 1 commit intomasterfrom
Conversation
red-hat-konflux
Bot
force-pushed
the
konflux/mintmaker/master/npm-minor-and-patch-dependencies
branch
8 times, most recently
from
8a11ddf to
21b47db
Compare
Chromatic Build
|
red-hat-konflux
Bot
force-pushed
the
konflux/mintmaker/master/npm-minor-and-patch-dependencies
branch
20 times, most recently
from
c171e2a to
3b0ce61
Compare
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
📝 WalkthroughWalkthroughUpdated Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
package.json (1)
132-132:⚠️ Potential issue | 🟠 Major
zod ^3.25.76bundles Zod v4 internally and is used at runtime in CLI validation—consider upgrading to v4 or moving to dependencies.Starting from v3.25.76,
zodshipszod v4bundled inside the v3 package, resulting in roughly 3.59 MB unpacked with significant overhead from the dual distribution. Sincezodis used for runtime validation in the CLI—via.safeParse()calls insrc/cli/cli.tsxandsrc/cli/commands/seeder.ts—it should either be independenciesrather thandevDependencies, or the project should upgrade tozod v4directly.Given that this project already targets TypeScript
^5.9.3(which satisfies zod v4's requirements) and v4 is now stable (v4.3.6+), upgrading to^4.0.0would be cleaner and eliminate the double-bundle overhead entirely.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@package.json` at line 132, The package.json currently lists "zod": "^3.25.76" which bundles Zod v4 internally and causes a double-distribution overhead used at runtime by CLI validation (calls to .safeParse() in src/cli/cli.tsx and src/cli/commands/seeder.ts); fix this by either moving the zod entry from devDependencies to dependencies or upgrade it to an official v4 release (e.g., "zod": "^4.0.0" or a newer stable v4.x.y) in package.json so the runtime CLI uses the proper v4 package rather than the bundled v4 inside v3.25.76—update lockfile (npm/yarn/pnpm) afterwards and run the CLI validation paths (.safeParse()) to verify nothing breaks.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@package.json`:
- Line 40: package.json currently lists "glob" in dependencies but it is only
used by build/dev scripts (scripts/createDataJson.js and
scripts/convert-patternfly-imports.js); move "glob" from "dependencies" to
"devDependencies" by removing the entry under dependencies and adding the same
version under devDependencies so runtime installs no longer include it and dev
tooling still has access.
---
Outside diff comments:
In `@package.json`:
- Line 132: The package.json currently lists "zod": "^3.25.76" which bundles Zod
v4 internally and causes a double-distribution overhead used at runtime by CLI
validation (calls to .safeParse() in src/cli/cli.tsx and
src/cli/commands/seeder.ts); fix this by either moving the zod entry from
devDependencies to dependencies or upgrade it to an official v4 release (e.g.,
"zod": "^4.0.0" or a newer stable v4.x.y) in package.json so the runtime CLI
uses the proper v4 package rather than the bundled v4 inside v3.25.76—update
lockfile (npm/yarn/pnpm) afterwards and run the CLI validation paths
(.safeParse()) to verify nothing breaks.
ℹ️ Review info
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge base: Disabled due to Reviews -> Disable Knowledge Base setting
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (1)
package.json
| "classnames": "^2.5.1", | ||
| "file-loader": "^6.2.0", | ||
| "glob": "^13.0.0", | ||
| "glob": "^13.0.6", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
# First, let's check the actual structure of package.json around the glob dependency
cat -n package.json | head -100Repository: RedHatInsights/insights-rbac-ui
Length of output: 4762
🏁 Script executed:
# Check specifically where glob is located in package.json
rg -n '"glob"' package.jsonRepository: RedHatInsights/insights-rbac-ui
Length of output: 100
🏁 Script executed:
# Check for any direct invocations of the glob CLI in project scripts and config files
echo "=== Checking package.json scripts for glob CLI usage ==="
rg -n '"glob ' package.json
echo "=== Checking for glob CLI usage in common locations ==="
fd -e js -e ts -e json -e sh . --max-depth 4 | xargs rg -l 'glob\b' 2>/dev/null | head -20Repository: RedHatInsights/insights-rbac-ui
Length of output: 413
🏁 Script executed:
# Check how glob is being used in the flagged files
echo "=== src/cli/commands/safety.ts ==="
rg -A 3 -B 3 'glob' src/cli/commands/safety.ts
echo "=== scripts/createDataJson.js ==="
rg -A 3 -B 3 'glob' scripts/createDataJson.js
echo "=== scripts/convert-patternfly-imports.js ==="
rg -A 3 -B 3 'glob' scripts/convert-patternfly-imports.jsRepository: RedHatInsights/insights-rbac-ui
Length of output: 2571
🏁 Script executed:
# Check if glob is imported as a module anywhere (would be safe in v13)
rg "import.*glob|require.*glob" --type=js --type=tsRepository: RedHatInsights/insights-rbac-ui
Length of output: 212
🏁 Script executed:
# Verify that these scripts are dev-only (not executed in production code)
echo "=== Checking if scripts are called from package.json ==="
rg -n '"createDataJson\.|"convert-patternfly' package.json
echo "=== Checking if these modules are imported from source code (not just build scripts) ==="
rg -r 'createDataJson|convert-patternfly' src/ 2>/dev/null || echo "No matches in src/"
echo "=== Confirm these are build/dev scripts only ==="
ls -la scripts/Repository: RedHatInsights/insights-rbac-ui
Length of output: 19066
Move glob to devDependencies — it's only used in build scripts.
The glob package is only consumed by build/dev scripts (scripts/createDataJson.js and scripts/convert-patternfly-imports.js) which use its JavaScript API. It should be listed under devDependencies, not dependencies.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@package.json` at line 40, package.json currently lists "glob" in dependencies
but it is only used by build/dev scripts (scripts/createDataJson.js and
scripts/convert-patternfly-imports.js); move "glob" from "dependencies" to
"devDependencies" by removing the entry under dependencies and adding the same
version under devDependencies so runtime installs no longer include it and dev
tooling still has access.
d39b95a to
fe84072
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
♻️ Duplicate comments (1)
package.json (1)
40-40:⚠️ Potential issue | 🟡 Minor
globin runtime dependencies still appears unresolved from prior review.This was previously flagged as dev-only usage; if still true, it should live in
devDependencies.#!/bin/bash set -euo pipefail echo "== glob declaration ==" rg -n '"glob"' package.json echo echo "== glob module usage ==" rg -nP --type=js --type=jsx --type=ts --type=tsx 'from\s+["'\'']glob["'\'']|require\(\s*["'\'']glob["'\'']\s*\)' || true echo echo "== glob usage in scripts folder ==" rg -nP '\bglob\b' scripts package.json || true🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@package.json` at line 40, The package.json currently lists "glob" as a runtime dependency but the reviewer found it’s only used for development tooling; move the "glob" entry from dependencies to devDependencies in package.json, update any lockfile (run npm/yarn/pnpm install) and verify there are no runtime imports of "glob" by searching the repo (the provided ripgrep commands) to ensure only build/scripts reference it; if any runtime imports exist, either refactor them to use a runtime-safe alternative or keep "glob" in dependencies and document why.
🧹 Nitpick comments (1)
package.json (1)
6-7: Tighten the npm engine floor for Node 24 parity.Your
.nvmrcspecifies Node24.13.1, which ships with npm11.6.1, but"npm": ">=7.24.2"allows npm from mid-2021—over 3 major versions behind. This inconsistency can lead to lockfile/install behavior divergence between development and CI environments. Align the npm floor to at least">=10.9.0"(Node 22 LTS standard) or">=11.6.0"(Node 24 parity). The lockfileVersion 3 requirement is already satisfied at these levels.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@package.json` around lines 6 - 7, The package.json engines entry currently pins "node": ">=22.22.0" but leaves "npm": ">=7.24.2", which is too low for the .nvmrc Node 24.13.1 environment; update the "npm" engine value in package.json (the "engines" object) to a tighter floor such as ">=11.6.0" (or at minimum ">=10.9.0" if you prefer Node 22 parity) so the npm runtime requirement matches Node 24 parity and prevents install/lockfile discrepancies.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@package.json`:
- Line 16: The package.json currently lists "@formatjs/cli": "6.13.0" under
dependencies but it's only used by the build scripts (translations:extract and
translations:compile); remove the "@formatjs/cli" entry from dependencies and
add the same version under devDependencies, then regenerate the lockfile (run
npm install or yarn install) so the lockfile reflects the move. Locate
references to "@formatjs/cli" in package.json and update dependency sections
accordingly.
---
Duplicate comments:
In `@package.json`:
- Line 40: The package.json currently lists "glob" as a runtime dependency but
the reviewer found it’s only used for development tooling; move the "glob" entry
from dependencies to devDependencies in package.json, update any lockfile (run
npm/yarn/pnpm install) and verify there are no runtime imports of "glob" by
searching the repo (the provided ripgrep commands) to ensure only build/scripts
reference it; if any runtime imports exist, either refactor them to use a
runtime-safe alternative or keep "glob" in dependencies and document why.
---
Nitpick comments:
In `@package.json`:
- Around line 6-7: The package.json engines entry currently pins "node":
">=22.22.0" but leaves "npm": ">=7.24.2", which is too low for the .nvmrc Node
24.13.1 environment; update the "npm" engine value in package.json (the
"engines" object) to a tighter floor such as ">=11.6.0" (or at minimum
">=10.9.0" if you prefer Node 22 parity) so the npm runtime requirement matches
Node 24 parity and prevents install/lockfile discrepancies.
ℹ️ Review info
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge base: Disabled due to data retention organization setting
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (1)
package.json
| "@data-driven-forms/common": "^4.1.13", | ||
| "@data-driven-forms/pf4-component-mapper": "^4.1.14", | ||
| "@data-driven-forms/react-form-renderer": "^4.1.13", | ||
| "@formatjs/cli": "6.13.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "== Checking package.json structure (dependencies section) =="
rg -n '"@formatjs/cli"' package.json -A 2 -B 2
echo
echo "== Checking lines 179-180 (build scripts) =="
sed -n '175,185p' package.json
echo
echo "== Checking for direct runtime imports =="
rg -nP --type=js --type=jsx --type=ts --type=tsx 'from\s+["'"'"']@formatjs/cli["'"'"']|require\(\s*["'"'"']@formatjs/cli["'"'"']\s*\)' || echo "No runtime imports found"
echo
echo "== Full dependencies vs devDependencies check =="
python3 <<'PYTHON'
import json
with open('package.json') as f:
data = json.load(f)
if '@formatjs/cli' in data.get('dependencies', {}):
print("@formatjs/cli is in: dependencies")
if '@formatjs/cli' in data.get('devDependencies', {}):
print("@formatjs/cli is in: devDependencies")
if '@formatjs/cli' not in data.get('dependencies', {}) and '@formatjs/cli' not in data.get('devDependencies', {}):
print("@formatjs/cli not found in either dependencies or devDependencies")
PYTHONRepository: RedHatInsights/insights-rbac-ui
Length of output: 1332
Move @formatjs/cli to devDependencies.
@formatjs/cli is used only in build-time scripts (translations:extract and translations:compile in package.json) and has no runtime imports. It should be in devDependencies, not dependencies.
Suggested manifest change
"dependencies": {
- "@formatjs/cli": "6.13.0",
...
},
"devDependencies": {
+ "@formatjs/cli": "6.13.0",
...
}🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@package.json` at line 16, The package.json currently lists "@formatjs/cli":
"6.13.0" under dependencies but it's only used by the build scripts
(translations:extract and translations:compile); remove the "@formatjs/cli"
entry from dependencies and add the same version under devDependencies, then
regenerate the lockfile (run npm install or yarn install) so the lockfile
reflects the move. Locate references to "@formatjs/cli" in package.json and
update dependency sections accordingly.
97b1d91 to
52068c7
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
♻️ Duplicate comments (1)
package.json (1)
16-16:⚠️ Potential issue | 🟡 MinorMove
@formatjs/cliandglobtodevDependencies.Line 16 and Line 40 still classify build-time tooling as runtime dependencies; this should stay dev-only.
Proposed manifest adjustment
"dependencies": { - "@formatjs/cli": "6.13.0", ... - "glob": "^13.0.6", ... }, "devDependencies": { + "@formatjs/cli": "6.13.0", + "glob": "^13.0.6", ... }#!/bin/bash set -euo pipefail echo "== Direct imports of `@formatjs/cli` or glob (all JS/TS sources) ==" rg -nP --type=js --type=jsx --type=ts --type=tsx \ 'from\s+["'"'"'](`@formatjs/cli`|glob)["'"'"']|require\(\s*["'"'"'](`@formatjs/cli`|glob)["'"'"']\s*\)' \ -g '!**/node_modules/**' echo echo "== package.json script usage (build-time) ==" rg -n '"translations:extract"|"translations:compile"|"glob"' package.jsonAlso applies to: 40-40
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@package.json` at line 16, package.json incorrectly lists build-time tools "@formatjs/cli" and "glob" under dependencies; move both entries from "dependencies" into "devDependencies" preserving their versions, update any package.json scripts if needed (e.g., translations:extract / translations:compile) to ensure tooling is invoked from devDependencies, run the package manager reinstall (npm/yarn/pnpm) to update lockfile, and verify there are no runtime imports of `@formatjs/cli` or glob in source files (search for import/require of "@formatjs/cli" or "glob") before finalizing the change.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@package.json`:
- Around line 6-7: Move `@formatjs/cli` and glob from "dependencies" into
"devDependencies" in package.json so they aren't installed in production (locate
the entries for "@formatjs/cli" and "glob" and cut/paste them under
"devDependencies"); then update your GitHub Actions workflow files to explicitly
pin node-version to at least "22.22.0" (find uses of actions/setup-node or
similar and set node-version to >=22.22.0 or a specific 22.22.x value) to match
the engine floor and ensure CI uses a compatible Node runtime.
---
Duplicate comments:
In `@package.json`:
- Line 16: package.json incorrectly lists build-time tools "@formatjs/cli" and
"glob" under dependencies; move both entries from "dependencies" into
"devDependencies" preserving their versions, update any package.json scripts if
needed (e.g., translations:extract / translations:compile) to ensure tooling is
invoked from devDependencies, run the package manager reinstall (npm/yarn/pnpm)
to update lockfile, and verify there are no runtime imports of `@formatjs/cli` or
glob in source files (search for import/require of "@formatjs/cli" or "glob")
before finalizing the change.
ℹ️ Review info
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge base: Disabled due to data retention organization setting
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (1)
package.json
| "node": ">=22.22.0", | ||
| "npm": ">=7.24.2" |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "== package.json engines =="
rg -n '"engines"|"node"|"npm"' package.json -A3 -B1
echo
echo "== GitHub Actions Node setup =="
if [ -d .github/workflows ]; then
fd -HI -e yml -e yaml . .github/workflows | xargs -r rg -n 'actions/setup-node|node-version|npm-version' || echo "No Node setup found in workflows"
else
echo "No .github/workflows directory found."
fi
echo
echo "== Docker base images using Node =="
fd -HI -t f 'Dockerfile*' . | xargs -r rg -n 'FROM\s+node:' || echo "No Dockerfile with Node found"
echo
echo "== package.json dependencies (formatjs/cli and glob) =="
rg -n '"@formatjs/cli"|"glob"' package.json -B1 -A1Repository: RedHatInsights/insights-rbac-ui
Length of output: 645
Move @formatjs/cli and glob to devDependencies and pin Node version in CI workflows.
-
@formatjs/cli(line 16) and glob (line 40) are build-time tools and must be in devDependencies, not dependencies. They should not be installed in production. -
No explicit Node version pin found in GitHub Actions workflows. With the engine floor now at Node >=22.22.0, workflows must be updated to explicitly pin node-version to at least 22.22.0 to ensure CI compatibility.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@package.json` around lines 6 - 7, Move `@formatjs/cli` and glob from
"dependencies" into "devDependencies" in package.json so they aren't installed
in production (locate the entries for "@formatjs/cli" and "glob" and cut/paste
them under "devDependencies"); then update your GitHub Actions workflow files to
explicitly pin node-version to at least "22.22.0" (find uses of
actions/setup-node or similar and set node-version to >=22.22.0 or a specific
22.22.x value) to match the engine floor and ensure CI uses a compatible Node
runtime.
44b53f3 to
62c4b4a
Compare
Code Review - Hermes AgentLooks GoodNo common issues detected. Reviewed by Hermes Agent |
Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
1 participant
This PR contains the following updates:
^7.28.6→^7.29.3^7.28.6→^7.29.0^7.28.6→^7.29.0^7.28.5→^7.29.0^7.28.6→^7.29.5^7.28.6→^7.29.2^7.28.6→^7.29.0^4.1.5→^4.1.15^4.1.6→^4.1.16^4.1.5→^4.1.146.8.8→6.14.5^30.2.0→^30.3.0^1.1.2→^1.1.5^6.4.0→^6.4.3^6.4.0→^6.4.3^1.57.0→^1.59.1^0.2.6→^0.5.0^3.0.12→^3.1.1^7.0.40→^7.4.1^6.7.51→^6.9.2^6.1.41→^6.6.1^7.0.36→^7.3.1^2.0.5→^2.0.6^9.0.0→^9.0.1^1.0.37→^1.1.1^3.4.1→^3.5.1^10.2.19→^10.3.6^4.0.2→^4.0.3^10.2.19→^10.3.6^0.24.2→^0.24.3^5.90.16→^5.100.9^5.91.2→^5.100.9^8.53.0→^8.59.2^8.53.0→^8.59.2^4.0.17→^4.1.5^4.0.17→^4.1.5^17.2.3→^17.4.2^10.2.8→^10.3.6^7.15.4→^7.16.2^13.0.0→^13.0.6^20.3.4→^20.9.0^30.2.0→^30.3.0^27.0.1→^27.4.0^2.12.7→^2.14.3^2.0.6→^2.0.7>=22.12.0→>=22.22.2>=7.0.0→>=7.24.2^1.57.0→^1.59.1^10.2.15→^10.3.6^29.4.6→^29.4.9^4.0.17→^4.1.5^5.104.1→^5.106.2^2.8.2→^2.8.4Release Notes
babel/babel (@babel/compat-data)
v7.29.3Compare Source
v7.29.3 (2026-04-30)
👓 Spec Compliance
babel-parser🐛 Bug Fix
babel-helper-create-class-features-plugin,babel-plugin-proposal-decoratorsbabel-register@babel/register(@liuxingbaoyu)babel-compat-data,babel-plugin-bugfix-safari-rest-destructuring-rhs-array,babel-preset-env💅 Polish
babel-parser📝 Documentation
🏃♀️ Performance
babel-helper-import-to-platform-api,babel-plugin-proposal-import-wasm-source,babel-plugin-transform-json-modulesCommitters: 4
v7.29.0Compare Source
v7.29.0 (2026-01-31)
Thanks @simbahax for your first PR!
🚀 New Feature
babel-typesbabel-standalone🐛 Bug Fix
babel-parserextendsclause (@nicolo-ribaudo)babel-traversebabel-plugin-transform-block-scoping,babel-traverse🏃♀️ Performance
babel-generator,babel-runtime-corejs3Committers: 6
data-driven-forms/react-forms (@data-driven-forms/common)
v4.1.15Compare Source
4.1.15 (2026-04-10)
🧱 Updated Dependencies
v4.1.14Compare Source
4.1.14 (2026-03-09)
🩹 Fixes
❤️ Thank You
v4.1.13Compare Source
4.1.13 (2026-02-16)
🧱 Updated Dependencies
v4.1.12Compare Source
4.1.12 (2026-02-11)
🩹 Fixes
🧱 Updated Dependencies
❤️ Thank You
v4.1.11Compare Source
4.1.11 (2026-02-09)
🧱 Updated Dependencies
v4.1.10Compare Source
4.1.10 (2026-02-05)
🩹 Fixes
🧱 Updated Dependencies
❤️ Thank You
v4.1.9Compare Source
4.1.9 (2026-02-04)
🚀 Features
🧱 Updated Dependencies
❤️ Thank You
v4.1.8Compare Source
4.1.8 (2026-02-02)
🧱 Updated Dependencies
v4.1.7Compare Source
4.1.7 (2026-02-02)
🧱 Updated Dependencies
v4.1.6Compare Source
4.1.6 (2026-01-21)
🚀 Features
🧱 Updated Dependencies
❤️ Thank You
jestjs/jest (@jest/test-sequencer)
v30.3.0Compare Source
Features
[jest-config]AdddefineConfigandmergeConfighelpers for type-safe Jest config (#15844)[jest-fake-timers]AddsetTimerTickModeto configure how timers advance[*]Reduce token usage when run through LLMs (3f17932)Fixes
[jest-config]Keep CLI coverage output when using--jsonwith--outputFile(#15918)[jest-mock]UseSymbolfrom test environment (#15858)[jest-reporters]Fix issue where console output not displayed for GHA reporter even withsilent: falseoption (#15864)[jest-runtime]Fix issue where user cannot utilize dynamic import despite specifying--experimental-vm-modulesNode option (#15842)[jest-test-sequencer]Fix issue where failed tests due to compilation errors not getting re-executed even with--onlyFailuresCLI option (#15851)[jest-util]Make sureprocess.features.require_moduleisfalse(#15867)Chore & Maintenance
[*]Replace remaining micromatch uses with picomatch[deps]Update to sinon/fake-timers v15[docs]Update V30 migration guide to notify users onjest.mock()work with case-sensitive path (#15849)mswjs/data (@msw/data)
v1.1.5Compare Source
v1.1.5 (2026-04-20)
Bug Fixes
orderByvalue (#362) (12d6d1a) @kettanaitov1.1.4Compare Source
v1.1.4 (2026-04-19)
Bug Fixes
rettime(#360) (fb3c509) @kettanaitov1.1.3Compare Source
v1.1.3 (2026-04-19)
Bug Fixes
75d80ca) @kettanaito0397d5c) @kettanaitoffa09aa) @kettanaito9f9845c) @kettanaitofa1c709) @kettanaito2ad167b) @kettanaitopatternfly/patternfly-react (@patternfly/react-core)
v6.4.3Compare Source
v6.4.2Compare Source
v6.4.1Compare Source
Updates Include:
- fix(Wizard): Fix crash in nav when first sub-step is hidden
- fix(CodeEditor): prevent focus loss (#12211)
- chore: Updated with snyk react router, and lodash requests
microsoft/playwright (@playwright/test)
v1.59.1Compare Source
Bug Fixes
codegen,--uiandshowcommands (#39990)v1.59.0Compare Source
🎬 Screencast
New page.screencast API provides a unified interface for capturing page content with:
Screencast recording — record video with precise start/stop control, as an alternative to the
recordVideooption:Action annotations — enable built-in visual annotations that highlight interacted elements and display action titles during recording:
screencast.showActions() accepts
position('top-left','top','top-right','bottom-left','bottom','bottom-right'),duration(ms per annotation), andfontSize(px). Returns a disposable to stop showing actions.Action annotations can also be enabled in test fixtures via the
videooption:Visual overlays — add chapter titles and custom HTML overlays on top of the page for richer narration:
Real-time frame capture — stream JPEG-encoded frames for custom processing like thumbnails, live previews, AI vision, and more:
Agentic video receipts — coding agents can produce video evidence of their work. After completing a task, an agent can record a walkthrough video with rich annotations for human review:
The resulting video serves as a receipt: chapter titles provide context, action annotations highlight each interaction, and the visual walkthrough is faster to review than text logs.
🔗 Interoperability
New browser.bind() API makes a launched browser available for
playwright-cli,@playwright/mcp, and other clients to connect to.Bind a browser — start a browser and bind it so others can connect:
Connect from playwright-cli — connect to the running browser from your favorite coding agent.
Connect from @playwright/mcp — or point your MCP server to the running browser.
Connect from a Playwright client — use API to connect to the browser. Multiple clients at a time are supported!
Pass
hostandportoptions to bind over WebSocket instead of a named pipe:Call browser.unbind() to stop accepting new connections.
📊 Observability
Run
playwright-cli showto open the Dashboard that lists all the bound browsers, their statuses, and allows interacting with them:🐛 CLI debugger for agents
Coding agents can now run
npx playwright test --debug=clito attach and debug tests overplaywright-cli— perfect for automatically fixing tests in agentic workflows:📋 CLI trace analysis for agents
Coding agents can run
npx playwright traceto explore Playwright Trace and understand failing or flaky tests from the command line:♻️
await usingMany APIs now return async disposables, enabling the
await usingsyntax for automatic cleanup:🔍 Snapshots and Locators
page.locator('body').ariaSnapshot().depthandmodein locator.ariaSnapshot().New APIs
Screencast
Storage, Console and Errors
filterin page.consoleMessages() and page.pageErrors() controls which messages are returned.Miscellaneous
livein tracing.start() for real-time trace updates.artifactsDirin browserType.launch() to configure the artifacts directory.🛠️ Other improvements
'retain-on-failure-and-retries'records a trace for each test run and retains all traces when an attempt fails — great for comparing a passing trace with a failing one from a flaky test.Known Issues⚠️ ⚠️
navigator.platformemulation can cause Ctrl or Meta dispatching errors (#40009). PassPLAYWRIGHT_NO_UA_PLATFORM = '1'environment variable while we are issuing a patch release. Let us know in the issue how it affected you.Breaking Changes⚠️
@playwright/experimental-ct-sveltepackage.Browser Versions
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.
To execute skipped test pipelines write comment
/ok-to-test.Documentation
Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.