Copying a release and changing git reference does not create a new deployment process snapshot

[mik-ky]

Severity

No response

Version

2026.1

Latest Version

I could reproduce the problem in the latest build

What happened?

Copying a release is a handy feature to pre-populate package versions.

When you copy a release in a version controlled project, and change the git ref, the UI displays this message:

This release will snapshot the deployment process from the head of the branch selected.

Despite the UI showing packages from the new deployment process, when you hit save and copy the release, the release created will still use the snapshot from the original release.

The copied release should use the snapshot from the changed git ref while pre-populating package versions where possible.

Reproduction

1. Upload two packages: A and B
2. Create a version-controlled project with a run a script step, referencing package A (main branch)
3. Create a new branch (v2), add another run a script step, referencing package B
4. Create a release from main branch
5. Copy this release - expand packages section and observe packages changing from 1 package to 2 packages when changing the git branch to v2
6. Finish copying the release
7. The create release is still using the old snapshot - package references in the release only shows package A

Error and Stacktrace

More Information

No response

Workaround

No response