-
Type: Bug
-
Status: Resolved
-
Priority: Minor
-
Resolution: Duplicate
-
Affects Version/s: 49
-
Fix Version/s: QualifiedToSchedule
-
Component/s: Versioning & Branch management
-
Tags:
When releasing a project using the "intermediate" branch mode on Studio, the "next" version change is not merged&pushed right away when releasing:
<application> - <version>3.8.4</version> + <version>3.8.5</version> <targetPlatform> <version>server-8.10</version> <packages>
(seen on the nuxeo-jenkins-report project when releasing version 3.8.4)
If another user in its own branch tries to release too, there may be a conflict on the next release version name.
Current workaround is to merge&push manually this change right after the release is done.
- is related to
-
NXS-4468 Create REST API endpoint to trigger Studio releases
- Resolved