fix(tag-from-scope), merge package.json props from the last snap #9207
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The need came from Angular components. Angular env uses ng-packgr to compile components during build, this tool modifies the package.json and adds different values into
exports
prop. Because the modification is done during build pipeline and is not saved as an artifact, it gets lost when tagging from scope.As a reminder, tag-from-scope copies artifacts from the last snap into the capsule and only runs the tag-pipeline.
This PR, uses the package.json saved in the last snap and merge its properties into the current package.json of the capsule. It can't simply replace it, because some values, such as
version
and dependencies versions are changed in this tag.