Skip to content

chore: 🤖 Updated uuid from v8.3.2 -> v11.1.1 for node-notifier - #3354

Open
andrewkim099 wants to merge 1 commit into
mainfrom
chore/update-uuid
Open

andrewkim099 wants to merge 1 commit into
mainfrom
chore/update-uuid

Conversation

@andrewkim099

@andrewkim099 andrewkim099 commented Sep 29, 2026 •

Copy link
Copy Markdown

Updated uuid from v8.3.2 -> v11.1.1 for node-notifier. This keeps the CommonJS-compatible version while addressing the older requested release.

✅ Closes: SECVULN-57198

Description

Added a pnpm override so the transitive uuid used by node-notifier resolves to 11.1.1
Ran npm install --lockfile-only

How to Test

Runpnpm why uuid --recursive to test

Checklist

- [ ] I have added before and after screenshots for UI changes
- [ ] I have added JSON response output for API changes

  • I have added steps to reproduce and test for bug fixes in the description
    - [ ] I have commented on my code, particularly in hard-to-understand areas
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
    - [ ] I have added a11y-tests label to run a11y audit tests if needed

PCI review checklist

  • I have documented a clear reason for, and description of, the change I am making.
    - [ ] If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
    - [ ] If applicable, I've documented the impact of any changes to security controls.
    Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.

Updated uuid from v8.3.2 -> v11.1.1 for node-notifier. Pin
node-notifier's transitive uuid dependency to 11.1.1.

✅ Closes: SECVULN-57198
@andrewkim099
andrewkim099 requested a review from a team as a code owner September 29, 2026 21:15
@hashicorp-cla-app

Copy link
Copy Markdown

CLA assistant check

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes


Andrew Kim seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA.
If you have already a GitHub account, please add the email address used for this commit to your account.

Have you signed the CLA already but the status is still pending? Recheck it.

This branch has not been deployed

No deployments
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.

1 participant