In December of 2018, many Node.js users noticed that their applications randomly returned an HTTP status code 502 "Bad Gateway" error. In this post, we'll show you how to resolve this issue if you have been affected.
The Liberty runtime is moving from a quarterly to a four-week release cycle. As a result, the buildpack will release new functions and fixes quicker. Users of the Liberty for Java buildpack will notice a few changes to the Liberty versions packaged with the buildpack.
We are deprecating the Application Management feature, and it will eventually be removed. With the removal of Application Management, your Node.js droplet will be smaller so your push times to the cloud could become shorter.
Starting with our next release, the IBM Node.js buildpack on IBM Cloud and IBM Cloud Private will provide the community edition binaries as a default.
By the end of the year we will pass several significant dates on the Node.js long-term support schedule. This post summarizes what this means and the version migration considerations.
Liberty buildpack v3.0 with the latest version of WebSphere Liberty is now deployed in Bluemix. It will be part of next week’s WebSphere Application Server V9 release and is now deployed in Bluemix. This makes the Liberty v9 runtime available in Bluemix first and a week ahead of the official release date!