Testing autochangelog update

[XxdpavelxX]

No description provided.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​pkgr/​core@​0.2.9
	@​octokit/​openapi-types@​18.0.0 ⏵ 24.2.0
	git-hooks-list@​1.0.3 ⏵ 4.1.1	+1		+3
	prettier-plugin-packagejson@​2.3.0 ⏵ 2.5.19			+9
	tinyglobby@​0.2.15
	@​octokit/​plugin-request-log@​1.0.4 ⏵ 4.0.1	+1		+1	+1
	@​octokit/​auth-token@​3.0.4 ⏵ 4.0.0	+1
	@​octokit/​rest@​19.0.13 ⏵ 20.1.2
	@​octokit/​endpoint@​9.0.0 ⏵ 9.0.6	+1		+1	+2
	@​octokit/​request-error@​5.0.0 ⏵ 5.1.1	+1	+5	+1	+2
	@​octokit/​graphql@​7.0.1 ⏵ 7.1.1	+1		+1	+1
	detect-indent@​6.1.0 ⏵ 7.0.2
	@​octokit/​request@​8.1.1 ⏵ 8.4.1	+1	+5	+1	+1
	sort-package-json@​1.57.0 ⏵ 3.4.0	+1
	fdir@​6.5.0
	@​octokit/​plugin-paginate-rest@​6.1.2 ⏵ 11.4.4-cjs.2	+1	+4
	synckit@​0.11.11
	eslint-config-prettier@​8.10.0 ⏵ 10.1.8	+1		+29
	@​octokit/​core@​4.2.4 ⏵ 5.2.2			+1
	@​octokit/​plugin-rest-endpoint-methods@​7.2.3 ⏵ 13.3.2-cjs.1	+1
	prettier@​2.8.8 ⏵ 3.6.2
	eslint-plugin-prettier@​4.2.1 ⏵ 5.5.4	+1
	@​metamask/​auto-changelog@​3.4.4 ⏵ 5.1.0	+5		+1	+15

View full report

[socket-security]

Caution

MetaMask internal reviewing guidelines:

• Do not ignore-all
• Each alert has instructions on how to review if you don't know what it means. If lost, ask your Security Liaison or the supply-chain group
• Copy-paste ignore lines for specific packages or a group of one kind with a note on what research you did to deem it safe.
  @SocketSecurity ignore npm/PACKAGE@VERSION

Action	Severity	Alert  (click "▶" to expand/collapse)
Block		[email protected] has Network access. Module: globalThis["fetch"] Location: Package overview From: package.json → npm/[email protected] ℹ Read more on: This package | This alert | What is network access? Next steps: 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 [email protected]. Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		[email protected] is a AI-detected potential code anomaly. Notes: No definitive malware detected in this fragment. The main security concern is supply-chain risk from dynamically loading plugins from potentially untrusted sources. To mitigate, enforce strict plugin provenance, disable remote plugin loading, verify plugin integrity, and apply least-privilege execution for plugins. Confidence: 1.00 Severity: 0.60 From: package.json → npm/[email protected] ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? Next steps: 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 [email protected]. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[cursor]

Bug: Hardcoded URL Breaks Multi-Platform Changelog

The auto-changelog command now uses a hardcoded repository URL (https://github.com/MetaMask/metamask-extension) instead of the dynamic GITHUB_REPOSITORY_URL environment variable. This breaks the script's intended multi-platform support, causing changelogs for other repositories (e.g., mobile) to incorrectly reference the extension repository.

 

[gauthierpetetin]

The repo shall not be hardcoded to "https://github.com/MetaMask/metamask-extension". It can also be "https://github.com/MetaMask/metamask-mobile".

[HowardBraham]

Oh, yes, that just had to be done so it could run in metamask-extension-test-workflow2