[Snyk] Security upgrade org.springframework.boot:spring-boot-starter-web from 3.4.11 to 3.5.15

[macroscope-cloud]

Snyk has created this PR to fix 1 vulnerabilities in the maven dependencies of this project.

Snyk changed the following file(s):

• examples/iOS-Hybrid-App-Java-Server/pom.xml

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score	Upgrade
	Allocation of Resources Without Limits or Throttling SNYK-JAVA-COMFASTERXMLJACKSONCORE-18517159	828	org.springframework.boot:spring-boot-starter-web: 3.4.11 -> 3.5.15 Proof of Concept

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Allocation of Resources Without Limits or Throttling

[macroscope-cloud]

This is a minor version upgrade, but it contains several breaking changes that require developer attention.

Key Breaking Changes:

• Removed Deprecated Code: The most significant change is the removal of classes, methods, and properties that were deprecated in Spring Boot 3.3 and marked for removal in 3.5. Applications using these will fail to compile after the upgrade.
• Stricter Profile Name Validation: Profile names are now validated more strictly and must only contain letters, digits, -, or _. Invalid names will cause startup failures.
• Actuator heapdump Endpoint: Access to the /actuator/heapdump endpoint is now disabled by default (access=NONE).
• Couchbase Capella SSL: The embedded SSL certificate for Couchbase Capella is no longer trusted automatically and requires manual configuration of an SSL bundle.
• Bean Condition Generics: The logic for conditional bean registration (@ConditionalOnMissingBean) now considers generics, which may alter which beans are created at startup.

There are no changes to the minimum Java version requirements for this upgrade.

Source: Spring Boot 3.5 Release Notes

Recommendation: Before upgrading, thoroughly review your codebase for any usage of APIs deprecated in Spring Boot 3.3. Check application profile names for compliance with the new validation rules and verify any conditional bean configurations that rely on generic types.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.