Skip to content

chore(deps): update dependency superagent to v10.3.0#536

Open
renovate[bot] wants to merge 2 commits intomainfrom
renovate/superagent-10.x-lockfile
Open

chore(deps): update dependency superagent to v10.3.0#536
renovate[bot] wants to merge 2 commits intomainfrom
renovate/superagent-10.x-lockfile

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Feb 11, 2026

This PR contains the following updates:

Package Change Age Confidence
superagent 10.2.310.3.0 age confidence

Release Notes

ladjs/superagent (superagent)

v10.3.0

Compare Source

  • fix: fixed package lock 5db8232
  • fix: fixed package lock b80038d
  • fix: add back zuul, fix mocha, xo, rimraf versions 829893c
  • fix: fixed deps 426c2bf
  • fix: fixed deps a55a6d6
  • fix: added back node v18 to tests c93aa19
  • chore: fix deps 5cd3751
  • Merge pull request #​1842 from hlovdal/dep_updates 68308c8
  • Merge pull request #​1839 from codders/feat/add-proxy-for-client-agent a488d25
  • chore: remove end-of-life nodejs versions and add active lts 170ef07
  • chore(deps): update eslint-plugin-compat package 3ce73dd
  • chore(deps): update tinify package a9a48a3
  • chore(deps): update xo package 5677b73
  • chore(deps): update rimraf package 7cda38c
  • chore(deps): update mocha package 608b4ef
  • chore(deps): update qs package 81719c9
  • chore(deps): remove zuul 7d8618b
  • chore(deps): update body-parser package e07aaaa
  • chore(deps): npm audit fix b4b2275
  • Merge pull request #​1837 from inseong01/translate-docs-ko cec2606
  • feat(client): add proxy object for request.agent for compatibility 44e68b1
  • docs: translate documents to ko_KR 624ab8c


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.

🔕 Ignore: Close this PR and you won't be reminded about this update 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 Feb 11, 2026

⚠️ No Changeset found

Latest commit: a736695

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

@nx-cloud
Copy link
Contributor

nx-cloud bot commented Feb 11, 2026

View your CI Pipeline Execution ↗ for commit a736695

Command Status Duration Result
nx run-many -t build --no-agents ✅ Succeeded <1s View ↗
nx affected -t build lint test typecheck e2e-ci ✅ Succeeded 1m 1s View ↗

☁️ Nx Cloud last updated this comment at 2026-03-05 16:00:13 UTC

@pkg-pr-new
Copy link

pkg-pr-new bot commented Feb 11, 2026

Open in StackBlitz

@forgerock/davinci-client

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

@forgerock/device-client

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

@forgerock/journey-client

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

@forgerock/oidc-client

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

@forgerock/protect

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

@forgerock/sdk-types

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

@forgerock/sdk-utilities

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

@forgerock/iframe-manager

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

@forgerock/sdk-logger

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

@forgerock/sdk-oidc

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

@forgerock/sdk-request-middleware

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

@forgerock/storage

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

commit: a736695

@github-actions
Copy link
Contributor

github-actions bot commented Feb 11, 2026

Deployed 25173b8 to https://ForgeRock.github.io/ping-javascript-sdk/pr-536/25173b893c145ae751ebdb2982136c51f1135a69 branch gh-pages in ForgeRock/ping-javascript-sdk

@github-actions
Copy link
Contributor

github-actions bot commented Feb 11, 2026

📦 Bundle Size Analysis

📦 Bundle Size Analysis

🆕 New Packages

🆕 @forgerock/journey-client - 87.3 KB (new)
🆕 @forgerock/journey-client - 0.0 KB (new)

➖ No Changes

@forgerock/sdk-logger - 1.6 KB
@forgerock/sdk-request-middleware - 4.5 KB
@forgerock/iframe-manager - 2.4 KB
@forgerock/sdk-oidc - 4.8 KB
@forgerock/storage - 1.5 KB
@forgerock/sdk-types - 7.9 KB
@forgerock/protect - 150.1 KB
@forgerock/device-client - 9.2 KB
@forgerock/davinci-client - 41.3 KB
@forgerock/sdk-utilities - 11.2 KB
@forgerock/oidc-client - 24.9 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

@codecov-commenter
Copy link

codecov-commenter commented Feb 11, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 14.74%. Comparing base (b89ad58) to head (a736695).
⚠️ Report is 58 commits behind head on main.

❌ Your project status has failed because the head coverage (14.74%) 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     #536      +/-   ##
==========================================
- Coverage   18.79%   14.74%   -4.06%     
==========================================
  Files         140      153      +13     
  Lines       27640    26262    -1378     
  Branches      980     1054      +74     
==========================================
- Hits         5195     3872    -1323     
+ Misses      22445    22390      -55     

see 49 files with indirect coverage changes

🚀 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/superagent-10.x-lockfile branch 2 times, most recently from a716306 to b37afe1 Compare February 12, 2026 17:47
nx-cloud[bot]

This comment was marked as outdated.

@renovate renovate bot force-pushed the renovate/superagent-10.x-lockfile branch 2 times, most recently from eaa19b3 to 043dae5 Compare February 18, 2026 21:41
@renovate renovate bot force-pushed the renovate/superagent-10.x-lockfile branch from 043dae5 to 4b5b381 Compare March 5, 2026 15:51
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 flaky task in your failed CI:

🔂 Since the failure was identified as flaky, we triggered a CI rerun by adding an empty commit to this branch.

Nx Cloud View detailed reasoning in Nx Cloud ↗


🎓 Learn more about Self-Healing CI on nx.dev

@renovate
Copy link
Contributor Author

renovate bot commented Mar 5, 2026

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

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.

1 participant