Skip to content

chore(deps): update dependency error-ex to v1.3.4 - #305

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/error-ex-1.x
Open

renovate[bot] wants to merge 1 commit into
masterfrom
renovate/error-ex-1.x

Conversation

@renovate

@renovate renovate Bot commented Oct 31, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
error-ex 1.3.2 → 1.3.4 age confidence

Release Notes

qix-/node-error-ex (error-ex)

v1.3.4

Compare Source

Functionally identical release to 1.3.2.

Version 1.3.3 is compromised. Please see debug-js/debug#1005.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "on tuesday and thursday,every weekend"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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

Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate
renovate Bot requested a review from a team as a code owner October 31, 2026 06:15
@vercel

vercel Bot commented Oct 31, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
faucet Ready Ready Preview Oct 31, 2026 6:15am UTC

Request Review

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 31, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-31T06:17:39.864028Z 393e1b4 PR opened
ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

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

Copy link
Copy Markdown

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: 393e1b4da3

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread apps/web/package.json
"is-arrayish": "0.3.2",
"simple-swizzle": "0.2.2",
"error-ex": "1.3.2"
"error-ex": "1.3.4"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Move the error-ex override to the root manifest

When CI or deployment runs the repository-pinned Yarn 4.3.1, this workspace-level entry has no effect: yarn install reports YN0057: web: Resolutions field will be ignored, and the committed yarn.lock still resolves error-ex to 1.3.2. Put the override in the root package.json and regenerate the lockfile; otherwise this dependency-update commit never installs 1.3.4.

Useful? React with 👍 / 👎.

This branch was successfully deployed

1 active deployment
Preview — 393e1b4d Deployed Oct 31, 2026 by vercel[bot]
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.

0 participants