Skip to content

Update SObject types for API 67 (Summer '26) - #33

Merged
nawforce merged 6 commits into
mainfrom
api-67
Jun 11, 2026
Merged

Update SObject types for API 67 (Summer '26)#33
nawforce merged 6 commits into
mainfrom
api-67

Conversation

@kjonescertinia

@kjonescertinia kjonescertinia commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

Updates the SObject stubs for the Salesforce Summer '26 (API 67.0) release and bumps the project version to 67.0.0.

Generation notes

  • Types were generated from a feature-loaded Summer '26 scratch org (created from config/org-all.json against the pre-release Dev Hub), which sees 4259 standard objects. Output from the existing pre-release org was overlaid additively for the few objects/fields only visible there (e.g. provisioned-network Feed fields). Suggest squash-merging as the history includes the earlier pre-release-only generation pass.
  • The merge into src was strictly additive — roughly 270 new standard objects and 1,500 new fields/relationships added, nothing removed. Custom and managed-package artifacts were excluded.
  • 14 reference fields where the org reported a different shape than the existing stubs kept their existing (manually fixed) types, e.g. the UsageResource.TokenResources duplicate-relationship fix.
  • The 8 Event Monitoring objects (ApiEvent, ListViewEvent, ReportEvent, PermissionSetEvent + stream/store variants) gained a json-type Records field in Summer '26 that the released force-partner-api client cannot deserialize. Their stubs were generated via the REST describe API instead, with output verified byte-identical to the SOAP generator on unaffected objects (json maps to String, as DescribedSObject already intended).
  • Three manual fixes of known generator artifacts: duplicate relationship names in CaseProceeding and GenAiPlannerDefinition, and a missing Blob import in ContentVersionRenditionContent.

Generator changes

  • SFConnection.fromSession allows authenticating with an sf CLI access token plus instance URL instead of username/password, since SOAP login() is retired (last supported API is 64.0).
  • Failing describe batches are retried per-object so one undeserializable SObject no longer aborts the other 99 in its batch.
  • config/org-all.json drops features retired in Summer '26 (Chatbot, CustomerDataPlatform, CustomerDataPlatformLite, EinsteinBuilderFree, and MarketingCloud which depends on one of them).

Versioning

  • pom.xml project version → 67.0.0, com.force.api test deps → 67.0.0, sf.apiVersion default → 67.0, README updated. The standard-types 67.0.0 dependency and MANIFEST were already in place.

Verified locally with mvn -B install -Dgpg.skip.

SOAP login() is retired so a password is not always practical. Passing
an https:// instance URL now treats the password argument as a session
ID. Also describe failing batches per-object so one SObject the WSC
client cannot deserialize does not lose the other 99.
Chatbot, CustomerDataPlatform, CustomerDataPlatformLite and
EinsteinBuilderFree are no longer valid scratch org features in
Summer '26, and MarketingCloud cannot be enabled without
CustomerDataPlatform.
Replaces the earlier pre-release org generation. The feature-loaded
scratch org sees 4259 standard objects vs 2260, giving much better
coverage. Output from the pre-release org was overlaid additively for
the few objects only visible there.
@nawforce
nawforce merged commit 59a03f8 into main Jun 11, 2026
1 check passed
@nawforce
nawforce deleted the api-67 branch June 11, 2026 21:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants