Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prevent updating dependencies in affected package.json #87

Open
2 of 4 tasks
nfantone opened this issue Apr 14, 2023 · 0 comments · May be fixed by #95
Open
2 of 4 tasks

Prevent updating dependencies in affected package.json #87

nfantone opened this issue Apr 14, 2023 · 0 comments · May be fixed by #95

Comments

@nfantone
Copy link

nfantone commented Apr 14, 2023

Issue type

  • bug report
  • idea
  • question
  • other

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 using yarn workspace: refs as versions in package.json, which yarn pack already takes care of resolving.

  • Before multi-semantic-release:
{
  "dependencies": {
    "@myorg/packageA": "workspace:^",
    "@myorg/packageB": "workspace:^",
    "express-winston": "^5.0.0"
  }
}
  • After multi-semantic-release:
{
  "dependencies": {
    "@myorg/packageA": "1.2.3",
    "@myorg/packageB": "2.4.1",
    "express-winston": "^5.0.0"
  }
}

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant