Fixes non-verbose for automated scripts like cron

A few cases of output were sent anyway, regardless of the verbose flag. Thus using cron, you get mailed with a few empty lines as output, especially when everything went fine.

👧

More managers, less backwards compatibility

When it is still allowed Debby breaks backwards compatibility 💥
Hey, it's still bèta (probably the last one by the way).

How to repair?

If you have a root_dir setting in your debby.json options files, change it to:

"check_composer": {
    "path": "/path/to/composerjson/"
}

And while you're at it...

Check npm

From this version you can also check the npm package manager!
If you have a package.json in your project root, it is picked up automatically. If not, you have to add the same setting as for composer:

"check_npm": {
    "path": "/path/to/packagejson/"
}

Verbose logging

Lastly, to help debugging, Debby has a verbose option. It is enabled automagically when running manually from the cli. But if you want it anyway, set verbose to 1 in the debby.json options file.

---

Onwards!

👧

Fixes Slack notifications for second updatable round

A special case, you needed:

• multiple updatable packages
• the first one already being notified before
• only a single updatable package which was not notified before
• Slack as a notification channel

😓

But now it is fixed :)

Allow platform packages in composer.json

From now on, Debby didn't really understand platform packages: packages like "php": ">=5.4.0" or "ext-curl": "*". It would check these packages at packagist and would fail. Now, these are skipped without furthers checks. They are not updatable in the same sense as normal packages.

Maybe later Debby actually checks them for outdated installs as well, but that might be a bit more tricky :)

Cache notifications so Debby can run daily

Debby was a bit spammy when she was set up to run daily. That single day was not enough time to update the package and Debby would just find the same update the next day again. Now she caches the updates she notified before and doesn't bother about that again.

Maybe later, she can remind you if you wait a month with updating :)

Fix exception during exception

When composer couldn't find out information about a package it would throw an exception. This exception was bugged causing an exception on an exception ...

More cowbell: notify Trello & Slack

Debby can talk over more channels: Trello & Slack. Next to already existing GitHub & email.

Also the readme is updated to cover all these use cases.

Extendable and less-composer specific

Internally a lot has changed. The interface stayed more or less the same.

Most importantly, the results from debby->check() is now an array of package objects.
With these objects, more information can be transfered in an easy way.

Further, the foundation is there to work with more channels and more package managers.

Notify via GitHub issues

Notify via creating issues at a GitHub repository.

This makes sending notifications via email an optional thing. You can choose which method to use.
Also, the Swift Mailer dependency is removed. Install it manually if you want to send notifications via email.

Improve notification emails

• Friendlier formatted emails
• Use short version of sha1 hashes
• Allow to disable all-fine mails
• Explain all-fine emails
• Explain updates above version constraints