You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
semantic-release finds that "command is not executed from the root of the cloned repository"
As a quick workaround, we can just lock the highest working semantic-release version in multi-sem-rel deps or in projects, for example, through yarn resolution hook:
The text was updated successfully, but these errors were encountered:
antongolub
changed the title
Looks to be incompatible with sem-rel versions upper than 15.13.24
Looks to be incompatible with sem-rel versions upper than 15.13.27
Oct 26, 2019
# [1.1.0](v1.0.3...v1.1.0) (2019-11-03)
### Bug Fixes
* **package:** add missed sem-rel plugins ([f3c9318](f3c9318))
* **package:** update execa to be compatible with sem-rel 15.13.28 ([069bb4e](069bb4e)), closes [#7](#7)
* force a release ([1e3ece5](1e3ece5))
### Features
* add execasync CLI flag to make execa calls be always synchronous ([693438c](693438c)), closes [#1](#1)
@dhoulb Hi, Dave.
semantic-release
got a big patch of its own deps, fixes, and It looks like it somehow affected multi-sem-rel.Here is what I can note:
There're a pair of meaningful troubles:
tagFormat
option is detected as invalidsemantic-release
finds that "command is not executed from the root of the cloned repository"As a quick workaround, we can just lock the highest working
semantic-release
version inmulti-sem-rel
deps or in projects, for example, through yarn resolution hook:The text was updated successfully, but these errors were encountered: