Skip to content

feat: add maxMergeSeqLength = 20 option in v3#761

Closed
G-Rath wants to merge 2 commits into
nodeca:v3from
G-Rath:backport
Closed

feat: add maxMergeSeqLength = 20 option in v3#761
G-Rath wants to merge 2 commits into
nodeca:v3from
G-Rath:backport

Conversation

@G-Rath

@G-Rath G-Rath commented Jun 17, 2026

Copy link
Copy Markdown

This backports 3de1b76 to v3 allowing GHSA-h67p-54hq-rp68 to be resolved downstream more easily.

While I would really like to just upgrade everything to v4, the change lands very cleanly and there's still a lot of use of v3 so I figured I'd see if people were open to releasing this :)

Resolves #762

@omgovich

Copy link
Copy Markdown

That would be really nice to have it in v3, since a lot of packages still use it.

G-Rath added a commit to ackama/rails-template that referenced this pull request Jun 22, 2026
- GHSA-8988-4f7v-96qf is due to `lighthouse` using an old version of
`@sentry/node` which [I've
upgraded](GoogleChrome/lighthouse#17079), we're
just waiting for a release on
- GHSA-h67p-54hq-rp68 is due to a dependency of Jest - I have done a
[backport to v3](nodeca/js-yaml#761) which I'm
hoping will get landed...
@omgovich

Copy link
Copy Markdown

@puzrin Hi! Any chance it could be merged?

@puzrin

puzrin commented Jun 26, 2026

Copy link
Copy Markdown
Member

Option gone in 5.2. Backported maxTotalMergeKeys instead. v3.15.0

@G-Rath

G-Rath commented Jun 26, 2026

Copy link
Copy Markdown
Author

Thanks, I've opened github/advisory-database#8152 to update the advisory to reflect the backport

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