When updating a package which contains an updated nested package, the nested package is correctly updated but then marked as modified, nesitating manually clicking ‘Undo Changes to Package’ on all nested packages every time a nested package is updated.
Repro
- Create the child package, I used a model containing a part.
- Create the parent package containing the child package, I used a model containing the package from (1).
- After ensuring both are up to date, create a handful of duplicates.
- Change the child package, e.g. change the part color.
- As specified in the documentation, first publish the child package, and then the parent package. The child and parent package instances that were modified are now up to date, but the other duplicates of the package require updating.
- Perform ‘Update All’ on one of the duplicate parent packages. Studio will warn you that you are modifying the child package.
- All package instances are now correctly updated to the latest version, but the child package in all the packages updated in (6) are marked as modified, and now must have their changes reverted. These reversions do not actually alter the package in any way.
Attempting to update the nested packages first will not work, as this causes the parent packages to be marked as altered, thus forcing you to revert the update to the child package.