Conversation
github-actions
Bot
added
the
size/L
|
Infisical secrets check: ✅ No secrets leaked! 💻 Scan logs2026-04-28T03:25:44Z INF scanning for exposed secrets...
3:25AM INF 576 commits scanned.
2026-04-28T03:25:45Z INF scan completed in 734ms
2026-04-28T03:25:45Z INF no leaks found
|
|
gstraccini
Bot
added
the
☑️ auto-merge
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
![gstraccini[bot]](https://avatars.githubusercontent.com/in/480132?s=60&v=4){kind=small}
guibranco
left a comment
guibranco
left a comment
There was a problem hiding this comment.
Automatically approved by gstraccini[bot]
|
Caution Review the following alerts detected in dependencies. According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.
|
||||||||||||
|
@depfu merge |
1 participant
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ jsdom (29.0.2 → 29.1.0) · Repo · Changelog
Release Notes
29.1.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 4 commits:
29.1.0Update dependencies and dev dependenciesSupport ratio CSS unit typeFix style cache invalidationRelease Notes
8.0.0
7.0.1
7.0.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Commits
See the full diff on Github. The new version differs by 26 commits:
11.3.5minify browser export11.3.4add browser esm export condition to not even try to load diagnostics channelcomment typocorrect comment (it's not about TLA)11.3.3Remove TLA, feature is DOA :(remove unnecessary unused internal exporttest to ensure TLA is not in use in node11.3.2add node esm dialect to avoid TLA11.3.1o11y: clarify 'get' options, organize get() methoddocs: mention tracing in the Status jsdocdocs: fix Status linksdocs: formattingdoc: typeo11.3.0changelog 11.3ci: skip on node 22, mocking dc is slightly badadd context to status/tracing objectsAdd tracing channels and diagnostic metricsadd diagnostic channel and polyfill for non-node envsupdate tap, tshy; cleanup build and ci stuffremove AbortController polyfillRelease Notes
8.0.1
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Commits
See the full diff on Github. The new version differs by 26 commits:
Bumped v7.25.0 (#5025)Bumped v7.24.8 (#5020)fix: avoid 401 failures for stream-backed request bodies (#4941) (#5006)chore: update v7.x maintenance release flowBumped v7.24.7 (#4947)ignore AGENTS.md (#4942)fix: correctly handle multi-value rawHeaders in fetch (#4938)test: skip IPv6 tests when IPv6 is not available (#4939)fix(types): Fix clone method type declaration to be an instance method rather than instance property (#4925)fix(types): align Response with DOM fetch types (#4867)test: skip flaky macOS Node 20 cookie fetch casesdoc: remove unused parameter `redirectionLimitReached` (#4933)docs: update broken links in file "Dispatcher.md" (#4924)Bumped v7.24.6 (#4931)test: auto-init WPT submodule (#4930)build(deps-dev): bump typescript from 5.9.3 to 6.0.2 (#4926)fix: avoid prototype collisions in parseHeaders (#4923)Revert "fix: assume http/https scheme for scheme-less proxy env vars (#4914)"fix: support Connection header with connection-specific header names per RFC 7230 (#4775)docs: clarify fetch and FormData pairing (#4922)fix: wrap kConnector call in try/catch to prevent client hang (#4834)fix(cache): check Authorization on request headers per RFC 9111 §3.5 (#4911)fix: assume http/https scheme for scheme-less proxy env vars (#4914)fix(websocket): support open diagnostics over h2 (#4921)fix(mock): improve error message when intercepts are exhausted (#4912)fix(test): client wasm compatible with clang 22 (#4909)🆕 @asamuzakjp/generational-cache (added, 1.0.1)
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands
Go to the Depfu Dashboard to see the state of your dependencies and to customize how Depfu works.