Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Oct 22, 2025

This PR contains the following updates:

Package Type Update Change Pending Age Confidence
node uses-with minor 22.14.0 -> 22.21.0 age confidence
@types/node (source) devDependencies minor 22.14.1 -> 22.18.10 22.18.12 (+1) age confidence

Release Notes

actions/node-versions (node)

v22.21.0: 22.21.0

Compare Source

Node.js 22.21.0

v22.20.0: 22.20.0

Compare Source

Node.js 22.20.0

v22.19.0: 22.19.0

Compare Source

Node.js 22.19.0

v22.18.0: 22.18.0

Compare Source

Node.js 22.18.0

v22.17.1: 22.17.1

Compare Source

Node.js 22.17.1

v22.17.0: 22.17.0

Compare Source

Node.js 22.17.0

v22.16.0: 22.16.0

Compare Source

Node.js 22.16.0

v22.15.1: 22.15.1

Compare Source

Node.js 22.15.1

v22.15.0: 22.15.0

Compare 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.


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

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

@changeset-bot
Copy link

changeset-bot bot commented Oct 22, 2025

⚠️ No Changeset found

Latest commit: b126d2a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@coderabbitai
Copy link

coderabbitai bot commented Oct 22, 2025

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Comment @coderabbitai help to get the list of available commands and usage tips.

@nx-cloud
Copy link
Contributor

nx-cloud bot commented Oct 22, 2025

View your CI Pipeline Execution ↗ for commit b126d2a

Command Status Duration Result
nx run-many -t build ✅ Succeeded <1s View ↗
nx affected -t build typecheck lint test e2e-ci ✅ Succeeded 1m 59s View ↗
nx-cloud record -- nx format:check ✅ Succeeded 1s View ↗

☁️ Nx Cloud last updated this comment at 2025-10-23 15:28:25 UTC

nx-cloud[bot]

This comment was marked as outdated.

@renovate renovate bot force-pushed the renovate/node-22.x branch from 220f941 to 67b7832 Compare October 22, 2025 21:44
nx-cloud[bot]

This comment was marked as outdated.

@renovate renovate bot force-pushed the renovate/node-22.x branch from 67b7832 to ff35e04 Compare October 22, 2025 23:02
nx-cloud[bot]

This comment was marked as outdated.

@renovate renovate bot force-pushed the renovate/node-22.x branch from ff35e04 to a3863b1 Compare October 22, 2025 23:12
@codecov-commenter
Copy link

codecov-commenter commented Oct 22, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 19.05%. Comparing base (9362959) to head (b126d2a).

❌ 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:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@renovate renovate bot force-pushed the renovate/node-22.x branch from a3863b1 to 8f6af34 Compare October 22, 2025 23:16
@pkg-pr-new
Copy link

pkg-pr-new bot commented Oct 22, 2025

Open in StackBlitz

@forgerock/davinci-client

pnpm add https://pkg.pr.new/ForgeRock/ping-javascript-sdk/@forgerock/davinci-client@440

@forgerock/oidc-client

pnpm add https://pkg.pr.new/ForgeRock/ping-javascript-sdk/@forgerock/oidc-client@440

@forgerock/protect

pnpm add https://pkg.pr.new/ForgeRock/ping-javascript-sdk/@forgerock/protect@440

@forgerock/sdk-types

pnpm add https://pkg.pr.new/ForgeRock/ping-javascript-sdk/@forgerock/sdk-types@440

@forgerock/sdk-utilities

pnpm add https://pkg.pr.new/ForgeRock/ping-javascript-sdk/@forgerock/sdk-utilities@440

@forgerock/iframe-manager

pnpm add https://pkg.pr.new/ForgeRock/ping-javascript-sdk/@forgerock/iframe-manager@440

@forgerock/sdk-logger

pnpm add https://pkg.pr.new/ForgeRock/ping-javascript-sdk/@forgerock/sdk-logger@440

@forgerock/sdk-oidc

pnpm add https://pkg.pr.new/ForgeRock/ping-javascript-sdk/@forgerock/sdk-oidc@440

@forgerock/sdk-request-middleware

pnpm add https://pkg.pr.new/ForgeRock/ping-javascript-sdk/@forgerock/sdk-request-middleware@440

@forgerock/storage

pnpm add https://pkg.pr.new/ForgeRock/ping-javascript-sdk/@forgerock/storage@440

commit: b126d2a

@github-actions
Copy link
Contributor

github-actions bot commented Oct 22, 2025

Deployed 4696bcb to https://ForgeRock.github.io/ping-javascript-sdk/pr-440/4696bcb8135a630b26cda86184d2e439b650540f branch gh-pages in ForgeRock/ping-javascript-sdk

@github-actions
Copy link
Contributor

github-actions bot commented Oct 22, 2025

📦 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
@forgerock/oidc-client - 23.0 KB
@forgerock/protect - 150.1 KB
@forgerock/sdk-utilities - 7.5 KB
@forgerock/sdk-types - 8.0 KB
@forgerock/storage - 1.4 KB
@forgerock/sdk-logger - 1.6 KB
@forgerock/iframe-manager - 2.4 KB
@forgerock/sdk-request-middleware - 4.4 KB
@forgerock/sdk-oidc - 2.5 KB
@forgerock/davinci-client - 35.4 KB


13 packages analyzed • Baseline from latest main build

Legend

🆕 New package
🔺 Size increased
🔻 Size decreased
➖ No change

ℹ️ How bundle sizes are calculated
  • Current Size: Total gzipped size of all files in the package's dist directory
  • Baseline: Comparison against the latest build from the main branch
  • Files included: All build outputs except source maps and TypeScript build cache
  • Exclusions: .map, .tsbuildinfo, and .d.ts.map files

🔄 Updated automatically on each push to this PR

@renovate renovate bot force-pushed the renovate/node-22.x branch 4 times, most recently from df886ad to 1f287b6 Compare October 23, 2025 00:08
nx-cloud[bot]

This comment was marked as outdated.

@renovate renovate bot force-pushed the renovate/node-22.x branch from 1f287b6 to c67a224 Compare October 23, 2025 00:32
Copy link
Contributor

@nx-cloud nx-cloud bot left a 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:

  1. 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.

  2. 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.

  3. 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
  4. 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.

  5. 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.

Nx CloudView in Nx Cloud ↗


🎓 To learn more about Self Healing CI, please visit nx.dev

@renovate renovate bot force-pushed the renovate/node-22.x branch from c67a224 to c48f26f Compare October 23, 2025 15:16
@renovate renovate bot force-pushed the renovate/node-22.x branch from c48f26f to b126d2a Compare October 23, 2025 15:25
@ryanbas21 ryanbas21 merged commit 129cfcd into main Oct 23, 2025
7 checks passed
@ryanbas21 ryanbas21 deleted the renovate/node-22.x branch October 23, 2025 15:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

3 participants