Skip to content

fix(deps): Update undici dependency to version 7.24.3#1014

Open
AIsofun wants to merge 2 commits intoopenclaw:mainfrom
AIsofun:main
Open

fix(deps): Update undici dependency to version 7.24.3#1014
AIsofun wants to merge 2 commits intoopenclaw:mainfrom
AIsofun:main

Conversation

@AIsofun
Copy link

@AIsofun AIsofun commented Mar 18, 2026

Update undici dependency to version 7.24.3
2026-03-18 19 16 59

Update undici dependency to version 7.24.3
@vercel
Copy link
Contributor

vercel bot commented Mar 18, 2026

@AIsofun is attempting to deploy a commit to the 0xBuns Team on Vercel.

A member of the Team first needs to authorize it.

@greptile-apps
Copy link
Contributor

greptile-apps bot commented Mar 18, 2026

Greptile Summary

This PR bumps the undici dependency in packages/clawdhub/package.json from ^7.24.0 to ^7.24.3, updating the minimum acceptable patch version (likely to pick up a security fix or bug fix in undici 7.24.3, as indicated by the screenshot in the PR description).

  • The change is minimal and low-risk: only the lower-bound of the semver range is updated within the same major/minor version.
  • No logic, configuration, or API surface is affected.
  • Per AGENTS.md, TypeScript should be verified clean before merging (bunx tsc -p packages/clawdhub/tsconfig.json --noEmit), though this is a pure runtime dependency with no type-only impact expected.
  • The PR title follows Conventional Commits format correctly (fix(deps): ...).

Confidence Score: 5/5

  • This PR is safe to merge — it is a patch-level dependency version bump with no logic or API changes.
  • The change is a single-line patch version constraint update for undici, confined to one package.json. There is no modified application code, no breaking API change, and the semver range (^7.x) ensures compatibility within the major version. Risk is minimal.
  • No files require special attention.

Last reviewed commit: "fix(deps): Update un..."

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: fb77f884e7

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

"p-retry": "^7.1.1",
"semver": "^7.7.4",
"undici": "^7.24.0"
"undici": "^7.24.3"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Update lockfile for undici dependency bump

After changing packages/clawdhub/package.json to undici: ^7.24.3, the workspace lock metadata is still undici: ^7.24.0 in bun.lock (line 83). This matters because CI/deploy run bun install --frozen-lockfile (.github/workflows/ci.yml:21, .github/workflows/deploy.yml:62), and Bun documents --frozen-lockfile as “Disallow changes to lockfile”; with this manifest/lock mismatch, frozen installs can fail before any build/test steps run.

Useful? React with 👍 / 👎.

@AIsofun
Copy link
Author

AIsofun commented Mar 19, 2026

Updated lockfile to match dependency bump.

@AIsofun
Copy link
Author

AIsofun commented Mar 19, 2026

Lockfile has been updated to resolve the frozen-lockfile issue.
Workflows are currently awaiting maintainer approval.

@AIsofun
Copy link
Author

AIsofun commented Mar 19, 2026

Summary

  • Bump undici from 7.24.0 → 7.24.3

Why

  • Includes upstream bug and potential security fixes in 7.24.3

Impact

  • Patch-level update (no breaking changes expected)
  • No runtime logic affected

Validation

  • Lockfile updated to match dependency change
  • CI should pass once workflows are approved

All review comments have been addressed.
This PR is ready to merge once workflows are approved.

@wisdomdaoleo

This comment was marked as spam.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants