Issue Summary

When running under Node 14, the error message printed out when a second instance of Ghost is trying to bind to a port isn't the custom one we have, but the generic one.

To Reproduce

1. Use Node 14
2. Run an instance of Ghost
3. Attempt to run another instance of Ghost on the same port
4. 💥

We have a check like error.errno === 'EADDRINUSE', which evals to `fa

Expected Behavior

It should be possible to customize the header of the generated changelog (or omit it completely).

Current Behavior

The changelog header is hardcoded in https://github.com/lerna/lerna/blob/master/core/conventional-commits/lib/constants.js

Possible Solution

A `command.publish.changelogHea

This is an issue in the markdown writer:

% pandoc -f native -s -t markdown
Pandoc (Meta {unMeta = fromList [("foo",MetaBool False)]})
[]
---
---

on latest develop, if I run:

go test
ERROR: 2020/10/09 16:43:21 oauth.go:148: viewOauthInit error: pretend unable to write state error
--- FAIL: TestViewOauthCallback (0.00s)
    --- FAIL: TestViewOauthCallback/success (0.00s)
        oauth_test.go:248: 
            	Error Trace:	oauth_test.go:248
            	Error:      	Received unexpected error:
            	            	/logi

It's not clear enough what to write into the source and destination fields.

Source -> Source (e.g. /path/)*
Destination -> Destination URL*

Validation?

• check if source has leading & trailing slash?
• check if destination is a valid url || has slashes?

In my plugin.xml has something like this inside:

<feature extension="dita.conductor.target.relative" file="integrator.xml"/>

but there is no "integrator.xml" in the plugin folder, the integrator complains:

        [integrate] D:\DITA-OT2.x\plugins\my.plugin\integrator.xml (The system cannot find the file specified)

but it is still successful.