Skip to content

Instantly share code, notes, and snippets.

@tbarbugli
Last active August 28, 2015 20:01
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save tbarbugli/1dfacf6051de73823085 to your computer and use it in GitHub Desktop.
Save tbarbugli/1dfacf6051de73823085 to your computer and use it in GitHub Desktop.
Stream call for API client update

Please update your API client

Introduction

Hello everyone, over the last months we made substantial infrastructure improvements to speed-up response time and make our APIs even more rock solid than before.

Most of these improvements became generally available transparently, unfortunately there are a few changes ready to go live soon that are not supported by our old API clients.

We strongly suggest you to upgrade your clients to the latest version available or at least make sure that your apps run on a recent version of the API client. In order to simplify this, we made a simple table with the clients and frameworks integrations. If the version of your client is listed in this table, you can stop reading this article and go back to building awesome stuff!

Package name Supported versions
stream-php ">=2.1.2, <2.2" or ">=2.2.2"
stream-js "~v2.2.2"
stream-node "~v0.3.0"
stream-python ">=2.2.1"
stream-ruby ">=2.2.3"
stream-java 0.1-RC2
stream-django ">=1.2.5"
stream-rails ">=2.3.1"
stream-laravel "~2.1"

If your API client is not supported (see table above) we strongly advise you to upgrade. All our official clients are built with forward compatibility in mind, this means that unless you were relying on private APIs or using some ancient alpha release, the upgrade will be very simple. As usual, please make sure you give your app a good test before using the new client in your production environment!

When should I update the client?

If you are using a client older than 6 months, you should upgrade right now. Chances are that you are missing out a tons of improvements in terms of performances and features. We will drop backward compatibility support for clients older than the specified version on 15 October 2015.

Need help?

In case you experience any issue with the upgrade or have any doubt about this, reach us at support@getstream.io.

Unofficial clients

All the unofficial clients that we know are not going to break with the new release of our API. If you are using a non official client and want to make sure that it will not break, send us an email at support@getstream.io.

PHP Client

If you are using the PHP client, you can choose between >=2.1.2, <2.2 and >=2.2.2. This is because the 2.1 branch will keep support for PHP 5.4 and Guzzle 5 and the 2.2 branch PHP 5.5 and Guzzle 6.

Is this call to upgrade related to some security leak?

Nope, the update is only required to support a few infrastrucural changes we made to our APIs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment