Skip to content

chore(openai-generator): fix vulnerable dependencies (npm audit fix)#5297

Open
EdgarPsda wants to merge 1 commit intoapostrophecms:mainfrom
EdgarPsda:fix-vulns
Open

chore(openai-generator): fix vulnerable dependencies (npm audit fix)#5297
EdgarPsda wants to merge 1 commit intoapostrophecms:mainfrom
EdgarPsda:fix-vulns

Conversation

@EdgarPsda
Copy link

Summary

Summarize the changes briefly, including which issue/ticket this resolves. If it closes an existing Github issue, include "Closes #[issue number]"

What are the specific steps to test this change?

For example:

1.- Go to the directory packages/openai-generator
2.- run npm audit you'll see 7 vulnerabilities (see .json file attached)

How fixed:

1.- Ran npm audit fix

  • Resolves previously reported HIGH and MEDIUM advisories in runtime dependencies.
  • No runtime code changes

Note: Only one moderate vulnerability is left, ESlint remediation requires a semver-major upgrade to ESlint 9, so it was intentionally left out to avoid conflicts in current CI jobs.

What kind of change does this PR introduce?

(Check at least one)

  • Bug fix
  • New feature
  • Refactor
  • Documentation
  • Build-related changes
  • Other

Make sure the PR fulfills these requirements:

  • It includes a) the existing issue ID being resolved, b) a convincing reason for adding this feature, or c) a clear description of the bug it resolves
  • The changelog is updated
  • Related documentation has been updated
  • Related tests have been updated

If adding a new feature without an already open issue, it's best to open a feature request issue first and wait for approval before working on it.

Other information:
audit.json

@BoDonkey
Copy link
Contributor

BoDonkey commented Feb 4, 2026

Hi @EdgarPsda - sorry for the delay in getting back to you. We just switched over to using a monorepo, so I'm not fully sure what you have permissions to do. But, can you try to run pnpm changeset, select the openai-generator repo, select a minor bump, and add a message for your change?
Thanks and thanks for this change!

@boutell
Copy link
Member

boutell commented Feb 4, 2026 via email

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.

3 participants