-
Notifications
You must be signed in to change notification settings - Fork 3
chore(devdeps): update dependency node to v22.21.0 #440
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
Conversation
|
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Comment |
|
View your CI Pipeline Execution ↗ for commit b126d2a
☁️ Nx Cloud last updated this comment at |
220f941 to
67b7832
Compare
67b7832 to
ff35e04
Compare
ff35e04 to
a3863b1
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. ❌ Your project status has failed because the head coverage (19.05%) is below the target coverage (40.00%). You can increase the head coverage or adjust the target coverage. Additional details and impacted files@@ Coverage Diff @@
## main #440 +/- ##
=======================================
Coverage 19.05% 19.05%
=======================================
Files 138 138
Lines 27477 27477
Branches 975 975
=======================================
Hits 5237 5237
Misses 22240 22240 🚀 New features to boost your workflow:
|
a3863b1 to
8f6af34
Compare
@forgerock/davinci-client
@forgerock/oidc-client
@forgerock/protect
@forgerock/sdk-types
@forgerock/sdk-utilities
@forgerock/iframe-manager
@forgerock/sdk-logger
@forgerock/sdk-oidc
@forgerock/sdk-request-middleware
@forgerock/storage
commit: |
|
Deployed 4696bcb to https://ForgeRock.github.io/ping-javascript-sdk/pr-440/4696bcb8135a630b26cda86184d2e439b650540f branch gh-pages in ForgeRock/ping-javascript-sdk |
📦 Bundle Size Analysis📦 Bundle Size Analysis🚨 Significant Changes🔻 @forgerock/journey-client - 0.0 KB (-82.0 KB, -100.0%) 📊 Minor Changes📈 @forgerock/journey-client - 82.0 KB (+0.0 KB) ➖ No Changes➖ @forgerock/device-client - 9.2 KB 13 packages analyzed • Baseline from latest Legend🆕 New package ℹ️ How bundle sizes are calculated
🔄 Updated automatically on each push to this PR |
df886ad to
1f287b6
Compare
1f287b6 to
c67a224
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.
Nx Cloud has identified a possible root cause for your failed CI:
Error Classification: environment_state
The failure is classified as environment_state rather than code_change because:
-
The PR changes are exclusively dependency version updates for Node.js runtime and type definitions - no business logic, test code, or application code was modified.
-
The dependency changes are minor version updates within the same major version (Node.js 22.14.0 → 22.21.0, @types/node 22.14.1 → 22.18.10), which should maintain API compatibility and not introduce breaking changes.
-
The test failure occurs in an end-to-end Playwright test (phone-number-field.test.ts) that depends on external services and timing. The error "element(s) not found" for the "Registration Complete" heading suggests the application flow did not complete as expected, which is characteristic of environmental issues such as:
- Backend service delays or unavailability
- Network latency affecting the DaVinci authentication flow
- Test environment state (database, authentication service)
- Race conditions in asynchronous operations
-
The subsequent timeout in the afterEach cleanup hook attempting to delete the user further indicates that the test environment state was compromised - the user was never properly created, so the cleanup cannot find the USER_DELETE button.
-
One test passed while one failed in the same test suite, suggesting intermittent behavior rather than a systematic code issue introduced by the dependency updates.
The failure does not appear to be related to the Node.js version bump or TypeScript type updates, as these would typically manifest as compilation errors, type mismatches, or consistent runtime failures across all tests, not isolated timing-related element visibility issues in a single end-to-end test.
A code change would likely not resolve this issue, so no action was taken.
🎓 To learn more about Self Healing CI, please visit nx.dev
c67a224 to
c48f26f
Compare
c48f26f to
b126d2a
Compare
This PR contains the following updates:
22.14.0->22.21.022.14.1->22.18.1022.18.12(+1)Release Notes
actions/node-versions (node)
v22.21.0: 22.21.0Compare Source
Node.js 22.21.0
v22.20.0: 22.20.0Compare Source
Node.js 22.20.0
v22.19.0: 22.19.0Compare Source
Node.js 22.19.0
v22.18.0: 22.18.0Compare Source
Node.js 22.18.0
v22.17.1: 22.17.1Compare Source
Node.js 22.17.1
v22.17.0: 22.17.0Compare Source
Node.js 22.17.0
v22.16.0: 22.16.0Compare Source
Node.js 22.16.0
v22.15.1: 22.15.1Compare Source
Node.js 22.15.1
v22.15.0: 22.15.0Compare Source
Node.js 22.15.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.