We would like multi-semantic-release to provide the option to avoid updating cross-references between interdependent packages with the next release version. This is particularly useful when using yarnworkspace: refs as versions in package.json, which yarn pack already takes care of resolving.
Ideally, both @myorg/packageA and @myorg/packageB should continue pointing to workspace:^ after a full release.
Actual behavior
Versions of affected dependents always get overridden by multi-semantic-release removing workspace: references and, ultimately, pushing changes to the repository.
Issue type
Expected behavior
We would like
multi-semantic-release
to provide the option to avoid updating cross-references between interdependent packages with the next release version. This is particularly useful when usingyarn
workspace:
refs as versions inpackage.json
, whichyarn pack
already takes care of resolving.multi-semantic-release
:multi-semantic-release
:Ideally, both
@myorg/packageA
and@myorg/packageB
should continue pointing toworkspace:^
after a full release.Actual behavior
Versions of affected dependents always get overridden by
multi-semantic-release
removingworkspace:
references and, ultimately, pushing changes to the repository.