So it appears that chocolatey broke the deployment pipeline again:
[3:43:18 AM] [semantic-release] » √ Created tag v2.1.0
[3:43:18 AM] [semantic-release] » i Start step "publish" of plugin "@semantic-release/exec"
[3:43:18 AM] [semantic-release] [@semantic-release/exec] » i Call script src\.build\semantic-release-publish.cmd 2.1.0
Running choco push...
Chocolatey v2.3.0
The default push source configuration is not set. Either pass a source to push to, such as `--source="'https://push.chocolatey.org/'"`, or set the `defaultPushSource` configuration value, for example `choco config set --name="'defaultPushSource'" --value="'https://push.chocolatey.org/'"`.
Running choco push complete. Errorlevel was 1
[3:43:19 AM] [semantic-release] » × Failed step "publish" of plugin "@semantic-release/exec"
[3:43:19 AM] [semantic-release] » × An error occurred while running semantic-release: { Error: Command failed with ENOENT: src\.build\semantic-release-publish.cmd 2.1.0
spawn src\.build\semantic-release-publish.cmd 2.1.0 ENOENT
Apparently we need to pass in some sort of flag to get this to build and that's why 24b02c757a2e446caf000d398bbc8358c9c34c53 built, tested, and tagged git okay, but didn't publish to chocolatey or github :/
So it appears that chocolatey broke the deployment pipeline again:
From https://ci.appveyor.com/project/activescott/lessmsi/builds/50196953#L1053
Apparently we need to pass in some sort of flag to get this to build and that's why 24b02c757a2e446caf000d398bbc8358c9c34c53 built, tested, and tagged git okay, but didn't publish to chocolatey or github :/