fix(publish): catch publish conflict 403 error from npm

[fahslaj]

Description

Catches another possible form of publish conflict error from npm.

Motivation and Context

Some permission setups on npm were causing a 403 error instead of the EPUBLISHCONFLICT code, and this ensures they are caught appropriately.

How Has This Been Tested?

This has been tested manually by publishing packages to npm with conflicts, observing the error in Lerna, then testing it again with this change and observing Lerna properly swallow the error.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Chore (change that has absolutely no effect on users)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[matheo]

@fahslaj a simple question please:
when will this be released? I imagine the releases comes as new stuff is done right? or is there any cadence?

[JamesHenry]

@matheo it's available in 7.1.1