When invoking Unity’s Package Manager with the -upmPack argument, the editor produces a valid, signed tarball of a package but still terminates with exit code 1. This non-zero return code can be misinterpreted by CI systems and packaging scripts as a failure, even though the pack operation completed successfully.

Steps to reproduce:

1. Run Unity in batch mode with the -upmPack option as indicated in the manual ([https://docs.unity3d.com/6000.3/Documentation/Manual/upm-signature.html])
2. Observe that a valid, signed tarball appears in the specified output folder.
3. Check the editor process’s exit code. It reports 1 instead of 0.

Expected results: 

Unity editor should exit with code 0 when -upmPack completes without errors.

Actual results: 

Unity editor exits with code 1 despite producing a correct, signed package.

Notes:

• CI pipelines and custom packaging scripts interpret the non-zero exit code as a failure, leading to false-negative build results.
• Users must implement manual workarounds to ignore or override the exit code.