How does AtomSphere handle deployment versions when packaging a process?

AtomSphere handles deployment versions by bundling the process along with all components that it references. This is crucial because when you deploy a process to a different environment, you need to ensure that every element that the process relies on—such as connections, data formats, and maps—is included. This guarantees that the process will function correctly in the new environment without missing any dependencies.

By including all referenced components in the package, AtomSphere facilitates a seamless deployment experience. This comprehensive approach reduces the chances of errors that could arise from missing components, which might lead to a failure in process execution after deployment. By ensuring that all dependencies are packaged together, AtomSphere provides a robust method for moving processes between different environments, thereby maintaining integrity and functionality.

The other options do not accurately reflect the behavior of AtomSphere in the context of deploying processes and their dependencies. Only packaging the main process would create significant risk for runtime issues, while ignoring references entirely would lead to incomplete deployments. Including only unchanged components does not capture the necessary changes that might impact the main process. Therefore, the correct understanding is that bundling the process along with all referenced components is fundamental for maintaining functionality post-deployment.