Skip to content

Conversation

@ericcrosson-bitgo
Copy link
Contributor

In CI currently[^1] we see the following logs

npm WARN exec The following package was not found and will be installed: multi-semantic-release

which means we're not locking our CI pipeline to a specific version
of multi-semantic-release.

This commit installs a specific version of multi-semantic-release
in the root package.json.

In CI currently[^1] we see the following logs

```
npm WARN exec The following package was not found and will be installed: multi-semantic-release
```

which means we're not locking our CI pipeline to a specific version
of multi-semantic-release.

This commit installs a specific version of multi-semantic-release
in the root package.json.
@ericcrosson-bitgo ericcrosson-bitgo requested a review from a team April 12, 2022 14:26
Copy link
Contributor

@bitgopatmcl bitgopatmcl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving since it looks like it does what it says. As mentioned, this isn't the cause of the current release failures so still looking into that.

@bitgopatmcl bitgopatmcl merged commit 914e9a1 into BitGo:master Apr 13, 2022
@github-actions
Copy link

🎉 This PR is included in version 1.0.0-beta.1 🎉

The release is available on npm package (@beta dist-tag)

Your semantic-release bot 📦🚀

@github-actions
Copy link

🎉 This PR is included in version 0.2.0-beta.1 🎉

The release is available on npm package (@beta dist-tag)

Your semantic-release bot 📦🚀

@github-actions
Copy link

🎉 This PR is included in version 0.1.1-beta.1 🎉

The release is available on npm package (@beta dist-tag)

Your semantic-release bot 📦🚀

@github-actions
Copy link

🎉 This PR is included in version 0.2.0-beta.1 🎉

The release is available on npm package (@beta dist-tag)

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants