Closed voronianski closed 4 years ago
I've just released Foundry v1.6.1 which contains a lot of dependency upgrades. Could you please try this version and check if the issue still occurs? Removing and reinstalling Foundry could also help.
The reason why we use semantic-release
's beta version is that it supports publishing from multiple branches, which the stable version doesn't. The beta has been in testing for over a year and is being used by many other users as well.
This should be fixed by #64, released in v2.0.0-beta.3
.
Description
Current version of
semantic-release
package introduces additional duplicate of@semantic-release/commit-analyzer
, e.g. lock file form website project -This leads to issues during install when beta version tar is not possible to download from NPM e.g.
error https://registry.yarnpkg.com/@semantic-release/commit-analyzer/-/commit-analyzer-7.0.0-beta-.2.tgz: Extracting tar content of undefined failed, the file appears to be corrupt: "Unexpected end of data
Solution
Possible way of fixing this is to clear this peer dependency hell related to
semantic-release
package. Is there any specific reason for usingsemantic-release
's beta instead of stable version?