This will break for people who have 4.x dictated by other packages, since you can't have 4 and 5 in parallel. I think we can use a ~4.0|~5.0 constraint or something similar to loosen it up. On holiday at the moment but will take a look when I can.

In the meanwhile, add:

    "repositories": [
        {
            "type": "git",
            "url": "https://github.com/Sjimi/slack"
        }
    ]

to your composer.json and update the version of maknz/slack to dev-master. A composer update will then give you the changes from your fork, without having to bother with Packagist etc.

Okay I had done this already for now. Let me know if you loosened the constraints though. Happy holidays.

Do you plan to update your composer.json @maknz? Because I use it in an app and I can't rely on a dev-master.

So 2 choices:

• You can update
• Or I have to clone and publish the package

I prefer the first one ;)

I was hesitant to push any updates while I have crappy mobile internet (until next week). But since this is clearly a problem I'll loosen the constraint now.