chore(deps): lock file maintenance

[renovate]

This PR contains the following updates:

Update	Change
lockFileMaintenance	All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "before 4am on monday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.

---

• Branch has one or more failed status checks

[github-actions]

Beta npm build

Maintainers can publish this PR to npm for fast testing.

Comment /publish-beta after the PR checks are green.

The workflow will:

• publish a prerelease package on the beta tag
• add a pinned pr-398 dist-tag for this exact PR build
• update this comment with the install command

Security note: beta publish is only enabled for branches inside this repository.

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	eslint@​10.11.0 ⏵ 9.39.5				-46
	@​angular/​platform-browser-dynamic@​19.2.15 ⏵ 19.2.25
	@​angular-eslint/​template-parser@​22.1.0 ⏵ 22.5.0
	@​angular/​language-service@​19.2.15 ⏵ 19.2.25			+1	+1
	@​angular/​common@​19.2.15 ⏵ 19.2.25	+1	+31
	@​capgo/​capacitor-updater@​8.47.10 ⏵ 8.52.1	+1			+2
	@​typescript-eslint/​parser@​8.70.0 ⏵ 8.71.1
	@​angular-devkit/​build-angular@​19.2.18 ⏵ 19.2.27	+1		+1	+1
	@​angular/​platform-browser@​19.2.15 ⏵ 19.2.25	+23
	@​types/​jasmine@​5.1.12 ⏵ 5.1.15	+25			+6
	@​angular/​animations@​19.2.15 ⏵ 19.2.25
	@​angular/​compiler-cli@​19.2.15 ⏵ 19.2.25	+1			+1
	@​angular/​forms@​19.2.15 ⏵ 19.2.25	+21
	@​angular/​cli@​19.2.18 ⏵ 19.2.27	+1		+1
	@​angular/​router@​19.2.15 ⏵ 19.2.25	+21
	@​angular/​core@​19.2.15 ⏵ 19.2.25	+18	+28
	@​angular/​compiler@​19.2.15 ⏵ 19.2.25	+20	+22
	@​typescript-eslint/​eslint-plugin@​8.70.0 ⏵ 8.71.1			+1
	@​types/​node@​24.10.2 ⏵ 24.19.1	+1		+1
	postcss@​8.5.2 ⏵ 8.5.29		+24		-2
	rimraf@​6.1.2 ⏵ 6.1.3	+1		+1
	@​angular-eslint/​builder@​22.1.0 ⏵ 22.5.0			+1
	@​angular-eslint/​schematics@​22.1.0 ⏵ 22.5.0			+9
	ionicons@​8.0.13 ⏵ 8.1.0
	zone.js@​0.16.2 ⏵ 0.16.3			+1	+2
	rollup@​4.53.3 ⏵ 4.64.0	+1	+16		+1
	@​angular-eslint/​eslint-plugin@​22.1.0 ⏵ 22.5.0			+1
	@​angular-eslint/​eslint-plugin-template@​22.1.0 ⏵ 22.5.0			+1
	prettier-plugin-java@​2.7.7 ⏵ 2.11.0				-1
	eslint@​10.11.0 ⏵ 10.12.0	+1
	prettier@​3.6.2 ⏵ 3.9.9	+1		+1
	@​ionic/​core@​8.7.7 ⏵ 8.8.19	-2			+1
See 5 more rows in the dashboard

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.

Priority	Alert  (click "▶" to expand/collapse)	Action
	Obfuscated code: npm @stencil/core is 70.0% likely obfuscated Confidence: 0.70 Location: Package overview From: example-app/package.json → npm/ionicons@8.1.0 → npm/@stencil/core@4.45.2 ℹ 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/@stencil/core@4.45.2. 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

View full report

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 738cbabe-62bf-4f0a-b045-d41c2b0709c5

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}