There's a section about Uninstall existing npm, but the recommendations for upgrading are scattered in the issues.

The relationship between node, npm and nvm is not clear and it's not obvious if upgrading npm should be done through nvm or at least in a way that doesn't break nvm.

New feature motivation

I've added semantic-release to some of my projects. Unfortunately, due to trial and error some of my pushes didn't get published. I can push a fix and thus publish a new release, but then the previous would-have-been release and its changelog seems to be lost. How would I recover or include the changelog of a failed release?

I had a look at the FAQ, but it only contai

Issue

In v7.1.0:

When you declare a custom file in bumpFiles standard-version will no longer update normal package.json, composer.json, lockfiles, etc. declared in the defaults.

This is fine (I don't think this is a bug because maybe you don't want it to bother with the defaults), but I think it should be mentioned in the documentation that when you do declare bumpFiles in your c

There is no mention of the --fish option in the README and its functionality is encapsulated by the --shell option, but --fish is still documented in the manpage and still works.

Some packages may bundle dependencies. We could report outdatedness for these the following way: for outdated packages with single download, propagate outdated status onto the download URL. Then we could show this download specially for other packages, or even make it affect the status.

When creating a CHANGELOG, if the commit that increased the version number is not the most recent commit, two version headings can be created. Also, the commit that increased the version number is discarded. when creating an initial release it is probably common to update the package.json file with more than just the version number.

Version 0.1.0

• Update remaining files

CVE-2018-19756 - Medium Severity Vulnerability

Vulnerable Library - expoios/2.10.6

The Expo platform for making cross-platform mobile apps

Library home page: https://github.com/expo/

Got this message:

? Are you using GitHub Enterprise? No
ERR! semantic-release Error: GitHub repository URL is invalid: https:undefined.git

This was caused by the repo being SSH based, not HTTP(s). Took a while to figure this out, a clearer error message would make sense and make this easily fixable.

Code here:
https://github.com/semantic-release/cli/blob/d2b48b0ef70e327ae591a3

Situation

At the moment, this project uses and supports Python 2.7. As we all know, Python 2.7 is going out of maintenance soon ("retire") and it's not clear what the project is going to do.

After disussing #160, we found out that the project doesn't have a clear statement or information regarding the retirement of Python 2.7 (neither in issues, README, nor documentation). Maybe I have mi

In order to help users, the wiki/README should expose a common failure section in which is described the problem of hosting a repository under the root directroy controlled by jgitver.

This occures when:

• your developping maven plugin with invoker integration tests
• you host a repository or the local repository in some sub directories

Getting this error when I try to use pgvm for postgres 9 or 9.5
advice?

We should add some logging to the library, as it's extremely hard to debug it when we have some problems.

I suggest that we add LogUtils like in Goldfinger and log at least:

• the response from the URL
• how is this response parsed and processed in the lib, especially when we