PM-10242: Add Finalizing status to DeployStatus enum for Spring '26 support#10
Conversation
…upport Co-Authored-By: arazkevich@prodly.co <devin@prodly.co>
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
📝 WalkthroughWalkthroughThe pull request increments the Maven artifact version from 64.0.0_12 to 64.0.0_13 and adds a new "Finalizing" enumeration value to the DeployStatus simple type in the WSDL metadata schema. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
Comment |
Summary
Adds the new
Finalizingstatus to theDeployStatusenum in the metadata WSDL. Salesforce introduced this new deployment status in their Spring '26 API version, and our current WSDL doesn't include it, causing aConnectionException: FinalizingNot a valid enumeration for type: class com.sforce.soap.metadata.DeployStatuswhen checking deployment status against Spring '26 sandboxes.Version bumped from
64.0.0_12to64.0.0_13.Review & Testing Checklist for Human
64.0.0_13offorce-wscandforce-metadata-api-with-rlmNotes
This is the first part of a two-part fix. After this PR is merged and the artifacts are published, the metadata-service will need to be updated to use the new version.
Link to Devin run: https://app.devin.ai/sessions/d8e9f833a55a4756b77ba2d3e0fe0b00
Requested by: @devin-prodly
Summary by CodeRabbit
New Features
Chores