Closed csantos-nydig closed 2 years ago
@GeeWizWow,
Could you take a look?
Hey @antongolub PR is open in #80.
FYI @csantos-nydig debug
can only be passed to sem-rel via CLI flags, as a result it does not do anything in your .releaserc.js
file, see debug in the sem-rel docs.
:tada: This issue has been resolved in version 6.5.1 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
Hey @antongolub PR is open in #80.
FYI @csantos-nydig
debug
can only be passed to sem-rel via CLI flags, as a result it does not do anything in your.releaserc.js
file, see debug in the sem-rel docs.
Thanks for the quick fix. I wonder if https://github.com/qiwi/multi-semantic-release/issues/79 is resolved by this change as well?
Thanks for the quick fix. I wonder if https://github.com/qiwi/multi-semantic-release/issues/79 is resolved by this change as well?
Given that debug
can only be enabled in semrel via the CLI entrypoint, which msr bypasses, instead using the programmatic entrypoint, #79 Would need be covered by a separate PR.
It would essentially require msr to lift code directly from the semrel codebase, specifically these lines:
Which may or may not be desirable, I can see arguments for both, I and agree the current behaviour highlighted in #79 is misleading.
Issue type
Expected behavior
flags passed to the CLI should override props configured in the config file when its passed down to
semantic-release
Actual behavior
.releaserc.js
config file is overriding the CLI glagsSteps to reproduce
I have a
.releaserc.js
with say this configuration:and I'm trying to run this command locally
While I see this at the start of my script (which is ok)
semantic-release gets
dryRun: false
THERE 👇 https://github.com/qiwi/multi-semantic-release/blob/888cb37426f5e0c6a93079e78e68476be046c0ea/lib/multiSemanticRelease.js#L202Possible solution
https://github.com/qiwi/multi-semantic-release/blob/888cb37426f5e0c6a93079e78e68476be046c0ea/lib/multiSemanticRelease.js#L184
I believe the order must be: