Henri d'Orgeval

## Integrate `license-checker` as a new kind of validation Create a new kind of validation for [license-checker](https://github.com/davglass/license-checker). Goal behind this would be that one would be able to verify if...

## Support `.publishrc.json` As a user I want to be able to rename the .publishrc to .publishrc.json at any time after the installation of publish-please

## have an option "warn" for validations Be able to publish even when a validation fails, without having to disable this validation in the .publishrc file

## Add npm shrinkwrap validation Be able to check the version in npm-shrinkwrap.json matches version in package.json and git tag

## Be able to run publish-please without emoji (-> delivered in v5.3.0) ```sh npm run publish-please --ci ```

## Be able to prevent publishing when a dependency points to github It would be great that publish-please detect any direct dependency to github or to local package file and...

Hi @BillyBlaze. Thank you for your great feedback. I did not know that publish-please was used in TeamCity. Because I am using TeamCity in my every day job, I fully...

@inikulin thank you for your suggestion. I will go your way and I suggest to create two internal reporters: one for elegant status and one for CI. At runtime, based...

Hi @BillyBlaze, your proposal has been published in version 5.3.0. See the [README](https://github.com/inikulin/publish-please/blob/master/README.md#running-in-ci-mode) for more details. Could you give it a try?

Hi @BillyBlaze, thank you very much for your feedback. I completely missed the point that characters like '√' '✓' '×' '✖' are not rendered correctly on Teamcity. I will solve...