Got an email this morning saying that SuiteCloud CLI version 4.0.0 is coming. The email says “Output for project validation, preview, and deployment will change across all SuiteCloud development tools. This includes progress information, summaries, warnings, and errors.“. It suggests testing your CI/CD pipeline but doesn’t outline the changes. Does anybody here know more about the changes? I didn’t see anything on the npm page.

I asked Claude to check the unmerged branches and draft a report

@michoel awesome! Thank you!

I wonder if this fixes the inconsistencies with the webstorm deploy vs cli deploy where it gives you all the warnings in one but not the other. I've had webstorm deploy fine but the CLI throws an error/warning.

Heads-up:

@oracle/suitecloud-cli

4.0.0 includes breaking changes. If your automation is affected and you are not ready to migrate, you can safely pin the CLI back to 3.2.0:

npm i @oracle/suitecloud-cli@3.2.0

We encourage you to try 4.0.0 locally first. If you hit a blocker (report it), switching back to 3.2.0 is straightforward. And a small automation-friendly Easter egg: try adding

--json

to your commands—especially:

suitecloud project:deploy --json

It produces structured output that is much easier for scripts and CI pipelines to consume.

Thanks @Ali Syed (NS DevTools QA) ! We use the CLI rather extensively. I’m sure that it’s absolutely perfect (just like all the code that we write) - but in the unlikely event that we do hit an issue, where do you want issues reported? GH?

Yes, GitHub will be perfect.

Roger that. Thanks for giving us all a new toy!

We’re excited too 😄 This one is a bit more than just a shiny new CLI. 4.0 is also using a new deployment backend under the hood. So while we’ve done our homework, there may still be a few real-world edge cases that need some tuning once everyone starts putting it through its paces. 😅 GitHub is the best place for issues for now. If you hit anything, drop it there and we’ll investigate! In any case you can DM as well.

regarding the new deployment backend, should we have any concerns about deploying with 3.x.x no longer working any time soon? very excited about the new version (and getting our automation on the new version) but also want to make sure we aren't in for any surprises with automation still using 3.x.x

@Jonathan MacKenzie For sure 3.x.x will stop working in future (with a proper notification in advance). Thats why suggesting to tryout 4.0.0 and let us know if you have any blockers.

Where can i see the breaking changes for CLI 4.0.0