Build: Release tooling for main

[kasperpeulen]

Closes #

What I did

How to test

Checklist

• Make sure your changes are tested (stories and/or unit, integration, or end-to-end tests)
• Make sure to add/update documentation regarding your changes
• If you are deprecating/removing a feature, make sure to update
  MIGRATION.MD

Maintainers

• If this PR should be tested against many or all sandboxes,
  make sure to add the ci:merged or ci:daily GH label to it.
• Make sure this PR contains one of the labels below.

["cleanup", "BREAKING CHANGE", "feature request", "bug", "documentation", "maintenance", "dependencies", "other"]

[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.

Issue	Package	Version	Note	Source
New author	clone-response	1.0.3	New Author: sindresorhus Previous Author: lukechilds	scripts/package.json via danger@11.2.6
New author	responselike	2.0.1	New Author: sindresorhus Previous Author: lukechilds	scripts/package.json via danger@11.2.6
Shell access	simple-git	3.19.0	Module: child_process Location: dist/cjs/index.js	scripts/package.json

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.

What is shell access?

This module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.

Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced.

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 package-name@version specifiers. e.g. @SocketSecurity ignore foo@1.0.0 bar@* or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore simple-git@3.19.0
• @SocketSecurity ignore clone-response@1.0.3
• @SocketSecurity ignore responselike@2.0.1

[socket-security]

New and updated dependency changes detected. Learn more about Socket for GitHub ↗︎

Packages		Version	New capabilities	Transitives1	Size	Publisher
danger	🆕	11.2.6	environment	+20	3.75 MB	orta
p-retry	🆕	5.1.2	None	+1	20.6 kB	sindresorhus
wait-on	🆕	7.0.1	None	+1	480 kB	jeffbski
@actions/core	🆕	1.10.0	network, filesystem, environment	+2	209 kB	thboop
dataloader	🆕	2.2.2	None	+0	62.2 kB	saihaj
jest-mock-extended	🆕	3.0.4	None	+1	144 kB	marchaos
simple-git	🆕	3.19.0	filesystem, shell	+2	898 kB	steveukx

Footnotes

1. https://docs.socket.dev ↩