[Snyk] Security upgrade com.force.api:force-partner-api from 64.0.3 to 67.0.0

[ashitsalesforce]

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

Snyk changed the following file(s):

• pom.xml

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score	Upgrade
	Allocation of Resources Without Limits or Throttling SNYK-JAVA-COMFASTERXMLJACKSONCORE-15365924	756	com.force.api:force-partner-api: 64.0.3 -> 67.0.0 Major version upgrade 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

[ashitsalesforce]

This upgrade spans multiple major Salesforce platform releases, from API version 64.0 to 67.0. While there are no direct breaking changes to the Java library's method signatures, there are significant versioned updates on the Salesforce platform that can alter behavior and require verification.

Key Changes by API Version:

• API v65.0 (Winter '26): Introduces runtime changes for Flows and Processes. For example, Data Tables in Flows now update automatically after field or language changes, which could affect UI-based automations.
• API v66.0 (Spring '26): Enforces stricter visibility for Apex class constructors.
• API v67.0 (Summer '26): Introduces significant security updates for Apex. Apex classes without a specified sharing declaration will now default to the more restrictive with sharing mode. Additionally, the WITH_SECURITY_ENFORCED SOQL clause is being deprecated in favor of explicit user or system mode.

Potential Impact:

The most critical change is the updated security behavior in API v67.0. If your application relies on Apex classes that implicitly used without sharing, those classes may now return fewer records, leading to unexpected behavior or errors in your application. This is a behavioral breaking change that depends on your specific Salesforce backend implementation.

Recommendation:
This upgrade carries a medium risk due to the underlying platform changes. Developers should thoroughly test their application's integration, paying close attention to any interactions with Apex classes and SOQL queries to ensure they are compatible with the new, stricter security defaults.

Source: Salesforce Release Notes for API versions 65.0, 66.0, and 67.0.

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