We changed bolt add recently to work if the dependency already existed in the repo, similar to yarn.
When using dist-tag versions, e.g. bolt add foo@latest, it will update workspace versions of that dependency to 'latest' rather than the resolved version. The original dependency version in the root package.json is correct.
I've confirmed that bolt upgrade works correctly so it's just an issue with bolt add.
We changed bolt add recently to work if the dependency already existed in the repo, similar to yarn.
When using dist-tag versions, e.g.
bolt add foo@latest, it will update workspace versions of that dependency to 'latest' rather than the resolved version. The original dependency version in the root package.json is correct.I've confirmed that
bolt upgradeworks correctly so it's just an issue withbolt add.