-
Notifications
You must be signed in to change notification settings - Fork 23
fix(deps): update npm minor and patch dependencies #207
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
fix(deps): update npm minor and patch dependencies #207
Conversation
6560682 to
857113d
Compare
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings. WalkthroughThis pull request updates dependency and devDependency versions in package.json for multiple libraries including data-driven-forms, PatternFly components, axios, react-intl, react-router-dom, yaml, Playwright, Red Hat frontend components/config, tsc-transform-imports, and ts-jest. No dependencies are added or removed. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
Comment |
35e9b7f to
3bcd890
Compare
551d65f to
d39038a
Compare
5fa536b to
88e8f23
Compare
88e8f23 to
9bd2036
Compare
Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
9bd2036 to
340f242
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@package.json`:
- Around line 24-42: The engines declaration in package.json is incompatible
with the PatternFly v6 dependencies; update the "engines" field's "node"
constraint to ">=18.0.0" to match PatternFly v6 requirements, or alternatively
downgrade the PatternFly packages (`@patternfly/react-core`,
`@patternfly/react-table`, `@patternfly/quickstarts` and related PatternFly v6
entries) to v5; locate the "engines" object in package.json and change the
"node" value to ">=18.0.0" (or pin the PatternFly package versions to v5) so the
declared Node version aligns with the installed PatternFly packages.
| "@data-driven-forms/pf4-component-mapper": "^4.1.7", | ||
| "@data-driven-forms/react-form-renderer": "^4.1.6", | ||
| "@monaco-editor/react": "^4.7.0", | ||
| "@patternfly/quickstarts": "^6.4.0", | ||
| "@patternfly/react-core": "^6.4.0", | ||
| "@patternfly/react-table": "^6.4.0", | ||
| "@patternfly/react-core": "^6.4.1", | ||
| "@patternfly/react-table": "^6.4.1", | ||
| "@redhat-cloud-services/frontend-components": "^6.1.1", | ||
| "@redhat-cloud-services/frontend-components-utilities": "^6.1.1", | ||
| "@redhat-cloud-services/types": "^2.0.3", | ||
| "@scalprum/react-core": "^0.11.1", | ||
| "@unleash/proxy-client-react": "^4.5.2", | ||
| "axios": "^1.13.2", | ||
| "axios": "^1.13.4", | ||
| "classnames": "^2.5.1", | ||
| "monaco-editor": "^0.55.1", | ||
| "react": "18.3.1", | ||
| "react-dom": "18.3.1", | ||
| "react-intl": "^6.6.2", | ||
| "react-router-dom": "^6.30.2", | ||
| "yaml": "^2.8.1" | ||
| "react-intl": "^6.8.9", | ||
| "react-router-dom": "^6.30.3", | ||
| "yaml": "^2.8.2" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
cat -n package.jsonRepository: RedHatInsights/learning-resources
Length of output: 2836
🌐 Web query:
Node 16 EOL end of life support 2024 2025 2026
💡 Result:
Node.js 16 (Gallium) official End-of-Life (EOL): September 11, 2023. After this date, the Node.js project no longer provides security fixes or bug fixes for Node 16. [1]
What that means for 2024 / 2025 / 2026
- 2024: Node 16 is already EOL the entire year (no upstream security/bug fixes). [1]
- 2025: Still EOL; many ecosystems/tools continue dropping it (e.g., AWS CDK ended support for Node 16 on May 30, 2025). [2]
- 2026: Still EOL; you should be on a supported LTS line (e.g., Node 20/22/24 depending on your constraints). [1]
Related security note (often relevant to Node 16)
- Node 16 commonly ties to OpenSSL 1.1.1, which is also EOL as of September 11, 2023 (no public security fixes from OpenSSL after that date). [3]
Sources: Node.js Release Working Group schedule [1], AWS CDK support notice [2], OpenSSL EOL notice [3].
[1] (github.com)
[2] (aws.amazon.com)
[3] (openssl-corporation.org)
Citations:
- 1: https://github.com/nodejs/Release
- 2: https://aws.amazon.com/blogs/devops/announcing-the-end-of-support-for-node-js-14-x-and-16-x-in-aws-cdk/?utm_source=openai
- 3: https://openssl-corporation.org/post/2023-09-11-eol-111/?utm_source=openai
🌐 Web query:
React 18.3.1 Node 16 compatibility requirements
💡 Result:
React 18.3.1 itself does not require Node 18+. The published react@18.3.1 package declares engines.node: ">=0.10.0", so Node 16 can install/use React 18.3.1 (from React’s own package constraints). [1]
What usually breaks on Node 16 is your tooling/dependencies around React, not React:
- Many modern packages in the React ecosystem have moved to Node >= 18 (example:
react-hook-formdeclaringengines.node: ">=18"and producingEBADENGINEon Node 16). [2] - Node 16 is end-of-life (no longer supported), so platforms/tools commonly drop it. [3]
Practical requirement: React 18.3.1 works with Node 16, but your app’s build stack (Next/Vite/TS/ESLint/etc.) may require Node 18+; upgrading to Node 18+ is the safe/default path. [2][3]
Sources: [1] UNPKG react@18.3.1 package.json, [2] react-hook-form issue showing Node>=18 engine enforcement, [3] Expo changelog noting Node 16 reached EOL and tooling moving to Node 18.
🌐 Web query:
PatternFly v6 Node 16 support requirements
💡 Result:
PatternFly v6 does not support Node.js 16 for development/building from the PatternFly repo.
- PatternFly v6 development requirement: Node.js ≥ 18.0.0 (Node 16 is below the minimum). (npmjs.com)
- If you must stay on Node 16, PatternFly’s npm docs show PatternFly 5 development required Node.js ≥ 16.0.0, so v5 is the compatible major line (not v6). (npmjs.com)
Citations:
- 1: https://www.npmjs.com/package/%40patternfly/patternfly?utm_source=openai
- 2: https://www.npmjs.com/package/%40patternfly/patternfly/v/6.0.0-alpha.4?utm_source=openai
Node 16 compatibility issue: PatternFly v6 requires Node >= 18, but engines field specifies >= 16.20.2.
Node 16 reached end-of-life on September 11, 2023 and no longer receives security updates. More critically, PatternFly v6.4.x (react-core, react-table, quickstarts) requires Node.js >= 18.0.0 for development and building, making it incompatible with the declared engine constraint of Node >= 16.20.2.
Update the engines field to "node": ">=18.0.0" or downgrade PatternFly packages to v5 if Node 16 support is required.
🤖 Prompt for AI Agents
In `@package.json` around lines 24 - 42, The engines declaration in package.json
is incompatible with the PatternFly v6 dependencies; update the "engines"
field's "node" constraint to ">=18.0.0" to match PatternFly v6 requirements, or
alternatively downgrade the PatternFly packages (`@patternfly/react-core`,
`@patternfly/react-table`, `@patternfly/quickstarts` and related PatternFly v6
entries) to v5; locate the "engines" object in package.json and change the
"node" value to ">=18.0.0" (or pin the PatternFly package versions to v5) so the
declared Node version aligns with the installed PatternFly packages.
This PR contains the following updates:
^4.1.4->^4.1.7^4.1.4->^4.1.6^6.4.0->^6.4.1^6.4.0->^6.4.1^1.56.1->^1.58.1^6.7.4->^6.7.51^1.0.26->^1.0.53^1.13.2->^1.13.4^6.6.2->^6.8.9^6.30.2->^6.30.3^29.4.5->^29.4.6^2.8.1->^2.8.2Release Notes
data-driven-forms/react-forms (@data-driven-forms/pf4-component-mapper)
v4.1.7Compare Source
4.1.7 (2026-01-21)
🚀 Features
🧱 Updated Dependencies
❤️ Thank You
v4.1.6Compare Source
4.1.6 (2026-01-14)
🩹 Fixes
🧱 Updated Dependencies
❤️ Thank You
v4.1.5Compare Source
4.1.5 (2025-11-25)
🚀 Features
❤️ Thank You
patternfly/patternfly-react (@patternfly/react-core)
v6.4.1Compare Source
microsoft/playwright (@playwright/test)
v1.58.1Compare Source
Highlights
#39036 fix(msedge): fix local network permissions
#39037 chore: update cft download location
#38995 chore(webkit): disable frame sessions on fronzen builds
Browser Versions
v1.58.0Compare Source
📣 Playwright CLI+SKILLs 📣
We are adding a new token-efficient CLI mode of operation to Playwright with the skills located at playwright-cli. This brings the long-awaited official SKILL-focused CLI mode to our story and makes it more coding agent-friendly.
Timeline
If you're using merged reports, the HTML report Speedboard tab now shows the Timeline:
UI Mode and Trace Viewer Improvements
Thanks to @cpAdm for contributing these improvements!
Miscellaneous
browserType.connectOverCDP() now accepts an
isLocaloption. When set totrue, it tells Playwright that it runs on the same host as the CDP server, enabling file system optimizations.Breaking Changes⚠️
_reactand_vueselectors. See locators guide for alternatives.:lightselector engine suffix. Use standard CSS selectors instead.devtoolsfrom browserType.launch() has been removed. Useargs: ['--auto-open-devtools-for-tabs']instead.Browser Versions
This version was also tested against the following stable channels:
v1.57.0Compare Source
Speedboard
In HTML reporter, there's a new tab we call "Speedboard":
It shows you all your executed tests sorted by slowness,
and can help you understand where your test suite is taking longer than expected.
Take a look at yours - maybe you'll find some tests that are spending a longer time waiting than they should!
Chrome for Testing
Starting with this release, Playwright switches from Chromium, to using Chrome for Testing builds. Both headed and headless browsers are subject to this. Your tests should still be passing after upgrading to Playwright 1.57.
We're expecting no functional changes to come from this switch. The biggest change is the new icon and title in your toolbar.
If you still see an unexpected behaviour change, please file an issue.
On Arm64 Linux, Playwright continues to use Chromium.
Waiting for webserver output
testConfig.webServer added a
waitfield. Pass a regular expression, and Playwright will wait until the webserver logs match it.If you include a named capture group into the expression, then Playwright will provide the capture group contents via environment variables:
This is not just useful for capturing varying ports of dev servers. You can also use it to wait for readiness of a service that doesn't expose an HTTP readiness check, but instead prints a readiness message to stdout or stderr.
Breaking Change
After 3 years of being deprecated, we removed
Page#accessibilityfrom our API. Please use other libraries such as Axe if you need to test page accessibility. See our Node.js guide for integration with Axe.New APIs
Locator.toString()now uses the description when available.stepsin locator.click() and locator.dragTo() that configures the number ofmousemoveevents emitted while moving the mouse pointer to the target element.PLAYWRIGHT_DISABLE_SERVICE_WORKER_NETWORKenvironment variable.PLAYWRIGHT_DISABLE_SERVICE_WORKER_CONSOLEenvironment variable.Browser Versions
RedHatInsights/frontend-components (@redhat-cloud-services/frontend-components-config)
v6.7.51Compare Source
v6.7.50Compare Source
v6.7.49Compare Source
v6.7.48Compare Source
v6.7.47Compare Source
v6.7.46Compare Source
v6.7.45Compare Source
v6.7.44Compare Source
v6.7.43Compare Source
v6.7.42Compare Source
v6.7.41Compare Source
v6.7.40Compare Source
v6.7.39Compare Source
v6.7.38Compare Source
v6.7.37Compare Source
v6.7.36Compare Source
v6.7.35Compare Source
v6.7.34Compare Source
v6.7.33Compare Source
v6.7.32Compare Source
v6.7.31Compare Source
v6.7.30Compare Source
v6.7.29Compare Source
v6.7.28Compare Source
v6.7.27Compare Source
v6.7.26Compare Source
v6.7.25Compare Source
v6.7.24Compare Source
v6.7.23Compare Source
v6.7.22Compare Source
v6.7.21Compare Source
v6.7.20Compare Source
v6.7.19Compare Source
v6.7.18Compare Source
v6.7.17Compare Source
v6.7.16Compare Source
v6.7.15Compare Source
v6.7.14Compare Source
v6.7.13Compare Source
v6.7.12Compare Source
v6.7.11Compare Source
v6.7.10Compare Source
v6.7.9Compare Source
v6.7.8Compare Source
v6.7.7Compare Source
v6.7.6Compare Source
axios/axios (axios)
v1.13.4Compare Source
v1.13.3Compare Source
Bug Fixes
Features
undefinedas a value in AxiosRequestConfig (#5560) (095033c)Reverts
Contributors to this release
formatjs/formatjs (react-intl)
v6.8.9Compare Source
Bug Fixes
v6.8.8Compare Source
Note: Version bump only for package react-intl
v6.8.7Compare Source
Bug Fixes
v6.8.6Compare Source
Note: Version bump only for package react-intl
v6.8.5Compare Source
Bug Fixes
v6.8.4Compare Source
Bug Fixes
v6.8.3Compare Source
Note: Version bump only for package react-intl
v6.8.2Compare Source
Note: Version bump only for package react-intl
v6.8.1Compare Source
Note: Version bump only for package react-intl
v6.8.0Compare Source
Bug Fixes
Features
v6.7.2Compare Source
v6.7.1Compare Source
Note: Version bump only for package react-intl
v6.7.0Compare Source
Bug Fixes
Features
v6.6.8Compare Source
Note: Version bump only for package react-intl
v6.6.7Compare Source
Note: Version bump only for package react-intl
v6.6.6Compare Source
Note: Version bump only for package react-intl
v6.6.5Compare Source
Note: Version bump only for package react-intl
v6.6.4Compare Source
Note: Version bump only for package react-intl
v6.6.3Compare Source
Note: Version bump only for package react-intl
remix-run/react-router (react-router-dom)
v6.30.3Compare Source
kulshekhar/ts-jest (ts-jest)
v29.4.6Compare Source
Bug Fixes
eemeli/yaml (yaml)
v2.8.2Compare Source
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.