chore(deploy): Release

[electron-builder-release-bot]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.

Releases

[email protected]

Minor Changes

• Emit download-progress events when downloading with multiple range differential downloader #9448 3533a3e @eliotschu

[email protected]

Patch Changes

• Fix: delete default macOS appPlist keys using extendInfo when set Nullish #9481 cb5b9c6 @Lemonexe
• Fix: pnpm "Invalid string length" errors during node module collection #9470 d38ae8e @danteissaias
• Fix: post-process parent directories of unpacked files to avoid overeager unpacking #9419 1c94529 @mmaietta
• Deprecate: warn about implicit publishing in CI #9475 ef43f42 @biw

Updated 2 dependencies

c3af390

• [email protected]
• [email protected]

[email protected]

Patch Changes

• Fix: update the dmgbuild hex regex for backgroundColor to be case insensitive #9487 c3af390 @Kilian

Updated 1 dependency

cb5b9c6 d38ae8e 1c94529 ef43f42

• [email protected]

[email protected]

Patch Changes

Updated 2 dependencies

cb5b9c6 d38ae8e 1c94529 ef43f42 c3af390

• [email protected]
• [email protected]

[email protected]

Patch Changes

Updated 1 dependency

cb5b9c6 d38ae8e 1c94529 ef43f42

• [email protected]

[email protected]

Patch Changes

Updated 1 dependency

cb5b9c6 d38ae8e 1c94529 ef43f42

• [email protected]

[email protected]

Patch Changes

Updated 1 dependency

cb5b9c6 d38ae8e 1c94529 ef43f42

• [email protected]

[email protected]

Patch Changes

Updated 1 dependency

cb5b9c6 d38ae8e 1c94529 ef43f42

• [email protected]

[email protected]

Patch Changes

Updated 1 dependency

cb5b9c6 d38ae8e 1c94529 ef43f42

• [email protected]

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	request@​2.88.2
	lazy-val@​1.0.5
	sanitize-filename@​1.6.3
	stat-mode@​1.0.0
	path-sort@​0.1.0
	resedit@​1.7.0
	simple-update-notifier@​2.0.0
	plist@​3.1.0
	jiti@​2.4.2
	js-yaml@​4.1.1
	prettier@​3.6.2

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Potential typosquat: npm query-ast as a typo of archived by owner Did you mean: [quarchived by ownery-ast](https://socket.dev/npm/package/archived by owner) From: pnpm-lock.yaml → npm/[email protected] → npm/[email protected] ℹ Read more on: This package | This alert | What is a typosquat? 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: Use care when consuming similarly named packages and ensure that you did not intend to consume a different package. Malicious packages often publish using similar names as existing popular packages. 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		Obfuscated code: npm markdown-it is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: pnpm-lock.yaml → npm/[email protected] ℹ Read more on: This package | This alert | What is obfuscated code? 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 not obfuscate their code. Consider not using packages with obfuscated code. 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		Deprecated by its maintainer: npm request Reason: request has been deprecated, see https://github.com/request/request/issues/3142 From: pnpm-lock.yaml → npm/[email protected] ℹ Read more on: This package | This alert | What is a deprecated package? 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: Research the state of the package and determine if there are non-deprecated versions that can be used, or if it should be replaced with a new, supported solution. 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