Release: Patch 7.6.17

[github-actions]

This is an automated pull request that bumps the version from 7.6.16 to 7.6.17.
Once this pull request is merged, it will trigger a new release of version 7.6.17.
If you're not a core maintainer with permissions to release you can ignore this pull request.

To do

Before merging the PR, there are a few QA steps to go through:

• Add the "freeze" label to this PR, to ensure it doesn't get automatically forced pushed by new changes.
• Add the "ci:daily" label to this PR, to trigger the full test suite to run on this PR.

And for each change below:

1. Ensure the change is appropriate for the version bump. E.g. patch release should only contain patches, not new or de-stabilizing features. If a change is not appropriate, revert the PR.
2. Ensure the PR is labeled correctly with one of: "BREAKING CHANGE", "feature request", "bug", "maintenance", "dependencies", "documentation", "build", "unknown".
3. Ensure the PR title is correct, and follows the format "[Area]: [Summary]", e.g. "React: Fix hooks in CSF3 render functions". If it is not correct, change the title in the PR.
   • Areas include: React, Vue, Core, Docs, Controls, etc.
   • First word of summary indicates the type: “Add”, “Fix”, “Upgrade”, etc.
   • The entire title should fit on a line

This is a list of all the PRs merged and commits pushed directly to next, that will be part of this release:

• 🔧 Maintenance: Core: Update ip version to fix CVE-2023-42282 #26086
• 🐛 Bug: Addon-docs: Fix Table of Contents heading leak #23677

🍒 Manual cherry picking needed!

The following pull requests could not be cherry-picked automatically because it resulted in merge conflicts.
For each pull request below, you need to either manually cherry pick it, or discard it by replacing the "patch:yes" label with "patch:no" on the PR and re-generate this PR.

• #26086: git cherry-pick -m1 -x ed46f1c725e13df5515c50dd6271d30292e8da7a

If you've made any changes doing the above QA (change PR titles, revert PRs), manually trigger a re-generation of this PR with this workflow and wait for it to finish. It will wipe your progress in this to do, which is expected.

Feel free to manually commit any changes necessary to this branch after you've done the last re-generation, following the Make Manual Changes section in the docs, especially if you're making changes to the changelog.

When everything above is done:

• Merge this PR
• Follow the run of the publish action

---

Generated changelog

7.6.17

• Addon-docs: Fix Table of Contents heading leak - #23677, thanks @ vmizg!
• Core: Update ip version to fix CVE-2023-42282 - #26086, thanks @ drik98!

[parthjmistry]

When are we planning to merge?

[valentinpalkovic]

I am doing the patch release now!

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/acorn@8.11.2	None	0	531 kB	marijn
npm/ws@8.15.1	environment, network	0	141 kB	lpinca

🚮 Removed packages: npm/punycode@2.3.0, npm/v8-to-istanbul@9.1.3, npm/ws@8.14.2

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source
New author	npm/loupe@2.3.7	New Author: keithamus Previous Author: chai	code/lib/instrumenter/package.json code/lib/test/package.json

View full report↗︎

Next steps

What is new author?

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/loupe@2.3.7