chore(openai-generator): fix vulnerable dependencies (npm audit fix)#5297
Open
EdgarPsda wants to merge 1 commit intoapostrophecms:mainfrom
Open
chore(openai-generator): fix vulnerable dependencies (npm audit fix)#5297EdgarPsda wants to merge 1 commit intoapostrophecms:mainfrom
EdgarPsda wants to merge 1 commit intoapostrophecms:mainfrom
Conversation
Contributor
|
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 |
Member
|
No permissions required! However "npm install -g pnpm" will be needed if
you don't yet have pnpm.
…On Wed, Feb 4, 2026 at 8:16 AM Robert Means ***@***.***> wrote:
*BoDonkey* left a comment (apostrophecms/apostrophe#5297)
<#5297 (comment)>
Hi @EdgarPsda <https://github.com/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!
—
Reply to this email directly, view it on GitHub
<#5297 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAH27MRNVP6XB67ICA3WX34KHWKXAVCNFSM6AAAAACTMWG2E6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQNBXGM4TQOBRGA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
--
THOMAS BOUTELL | CHIEF EXECUTIVE OFFICER
APOSTROPHECMS | apostrophecms.com | he/him/his
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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:
How fixed:
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)
Make sure the PR fulfills these requirements:
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