build(deps): bump docker/metadata-action from 5.10.0 to 6.1.0

[dependabot]

Bumps docker/metadata-action from 5.10.0 to 6.1.0.

Release notes

Sourced from docker/metadata-action's releases.

v6.1.0

• Bump @​docker/actions-toolkit from 0.79.0 to 0.90.0 in docker/metadata-action#613
• Bump brace-expansion from 1.1.12 to 5.0.6 in docker/metadata-action#658 docker/metadata-action#630
• Bump csv-parse from 6.1.0 to 6.2.1 in docker/metadata-action#617
• Bump fast-xml-parser from 5.4.2 to 5.8.0 in docker/metadata-action#620
• Bump flatted from 3.3.3 to 3.4.2 in docker/metadata-action#623
• Bump glob from 10.3.15 to 10.5.0 in docker/metadata-action#621
• Bump handlebars from 4.7.8 to 4.7.9 in docker/metadata-action#629
• Bump lodash from 4.17.23 to 4.18.1 in docker/metadata-action#639
• Bump moment-timezone from 0.6.0 to 0.6.1 in docker/metadata-action#619
• Bump picomatch from 4.0.3 to 4.0.4 in docker/metadata-action#626
• Bump postcss from 8.5.6 to 8.5.10 in docker/metadata-action#649
• Bump tar from 6.2.1 to 7.5.15 in docker/metadata-action#657
• Bump undici from 6.23.0 to 6.25.0 in docker/metadata-action#614
• Bump vite from 7.3.1 to 7.3.2 in docker/metadata-action#637

Full Changelog: docker/metadata-action@v6.0.0...v6.1.0

v6.0.0

• Node 24 as default runtime (requires Actions Runner v2.327.1 or later) by @​crazy-max in docker/metadata-action#605
• List inputs now preserve # inside values while still supporting full-line # comments by @​crazy-max in docker/metadata-action#607
• Switch to ESM and update config/test wiring by @​crazy-max in docker/metadata-action#602
• Bump lodash from 4.17.21 to 4.17.23 in docker/metadata-action#588
• Bump @​actions/core from 1.11.1 to 3.0.0 in docker/metadata-action#599
• Bump @​actions/github from 6.0.1 to 9.0.0 in docker/metadata-action#597
• Bump @​docker/actions-toolkit from 0.68.0 to 0.79.0 in docker/metadata-action#604
• Bump @​isaacs/brace-expansion from 5.0.0 to 5.0.1 in docker/metadata-action#600
• Bump semver from 7.7.3 to 7.7.4 in docker/metadata-action#603

Full Changelog: docker/metadata-action@v5.10.0...v6.0.0

Commits

• 80c7e94 Merge pull request #613 from docker/dependabot/npm_and_yarn/docker/actions-to...
• 8e0ddab chore: update generated content
• a8db14b chore(deps): Bump @​docker/actions-toolkit from 0.79.0 to 0.90.0
• 63a7371 Merge pull request #617 from docker/dependabot/npm_and_yarn/csv-parse-6.2.0
• c6916a6 chore: update generated content
• aca9205 chore(deps): Bump csv-parse from 6.1.0 to 6.2.1
• 9dcfe60 Merge pull request #629 from docker/dependabot/npm_and_yarn/handlebars-4.7.9
• 43dea76 chore: update generated content
• 7a56f5a chore(deps): Bump handlebars from 4.7.8 to 4.7.9
• e49e0aa Merge pull request #658 from docker/dependabot/npm_and_yarn/brace-expansion-5...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[changeset-bot]

⚠️ No Changeset found

Latest commit: a70a105

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​angular/​platform-browser-dynamic@​19.2.17
	@​angular/​platform-browser@​19.2.17
	@​tailwindcss/​cli@​4.1.1
	@​sveltejs/​package@​2.5.7
	@​angular/​animations@​19.2.17
	@​npmcli/​arborist@​9.7.0
	@​angular/​cli@​19.2.15
	@​angular/​compiler@​19.2.18
	@​tailwindcss/​postcss@​4.1.12
	@​mjackson/​form-data-parser@​0.9.1
	@​mjackson/​file-storage@​0.7.0
	@​aws-sdk/​client-sts@​3.1047.0
	@​aws-sdk/​s3-presigned-post@​3.1047.0
	@​aws-sdk/​client-s3@​3.986.0
	@​aws-sdk/​s3-request-presigner@​3.1047.0 ⏵ 3.986.0

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		Obfuscated code: npm @mswjs/interceptors is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/@mswjs/interceptors@0.41.9 ℹ 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 support@socket.dev. 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/@mswjs/interceptors@0.41.9. 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 @noble/hashes is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/@noble/hashes@1.8.0 ℹ 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 support@socket.dev. 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/@noble/hashes@1.8.0. 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 @noble/hashes is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/@noble/hashes@1.8.0 ℹ 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 support@socket.dev. 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/@noble/hashes@1.8.0. 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