Bot releases are visible (Hide)
Published by webpro almost 7 years ago
Published by webpro almost 7 years ago
dist.stageDir
(closes #169) (08e086b)Published by webpro almost 7 years ago
Published by webpro almost 7 years ago
Published by webpro almost 7 years ago
Breaking change: support for Node v4 has been dropped.
Published by webpro almost 7 years ago
Published by webpro almost 7 years ago
allowFromSubmodule
flag and don't throw if inside one (ca92020)Published by webpro almost 7 years ago
changelogCommand
(fixes #150) (125f9b8)config.assignOptions
to config instance (ac35aef)Published by webpro almost 7 years ago
Published by webpro almost 7 years ago
Published by webpro almost 7 years ago
Published by webpro almost 7 years ago
Note: anonymous data is collected at the start and end of a release-it session. This data includes:
buildCommand
(not the command itself), preRelease
I would like to have an idea of the number of (successful) runs, and how it is used. Currently the only vague indication is download stats at the npm project page, and GitHub stars.
Published by webpro almost 7 years ago
Breaking change: see 4.0.0-rc.0
Published by webpro almost 7 years ago
Published by webpro about 7 years ago
Breaking change
In short, this does not affect you if you didn't use the !
prefix in command hooks such as buildCommand
.
Before, the buildCommand
and other command hooks could have a !
prefix to enforce it not to use ShellJS internal commands. This was especially required for combined commands such as "!npm test && npm run build"
. However, from release-it v4, the default is to always resort to shell.exec
. To enforce usage of internal ShellJS commands, the command should be prefixed with !
(e.g. "!mkdir -p build"
).
Published by webpro about 7 years ago
Published by webpro about 7 years ago
Published by webpro about 7 years ago
Published by webpro about 7 years ago
Published by webpro about 7 years ago
shouldReject
(b0b78ce)