Codeship changelog codeship.com

We’re happy to announce that our new Github integration (based on Github Apps) is now live!

Practically, this means that you will be asked to re-authenticate with Github, and that the way you create projects have changed slightly. Take a look at the blog post if you’re interested in how the new flow looks and works. It also means that you can start migrating projects from the old Github integration to the new integration, something that unfortunately requires manual input and needs to be done before Jan 31, 2019. Please see the blog post linked above for more detail.

Please reach out to us with any questions or issue you might find.

Just a quick heads-up that the way you login to CodeShip with your Github account, and the way you create projects, is going to change end of September.

You don’t need to do anything. We just wanted to make sure you wouldn’t be surprised when you’re asked to login with Github again, and things look a bit different. We’ll announce a maintenance window for when the changes will roll out.

Please see the blog post for more details about the what, why, and when, and reach out to us with any questions or issue you might find.

Once the changes are rolled out, you can start to migrate your projects to the new Github integration. Please do so before Jan 31st, 2019 or your build will cease to work. It’s fast and easy, but requires manual input on Github to allow our new Codeship App access to your organization.

Today we updated a couple of PHP minor versions:

• 7.1.20 -> 7.1.21
• 7.2.8 -> 7.2.9

We're happy to announce, that today we made support for sudo commands on CodeShip Basic available for everyone. We’ve tested this in private beta for several months and are confident this will help make you even more productive.

If you have a package that requires root, or other scripts/libraries that need administrative access, you can now add them to your project. There are a few limitations (e.g. no virtualization), but you can read more about that on the documentation page.

As promised, data access for Shipscope has been turned off effective today, August 17. If you have Shipscope installed in Chrome, it will no longer be able to send you alerts about your CodeShip activity.

For fine-grained control of build notifications, update your notification preferences under Project Settings -> Notifications. Browser notifications can also be enabled on your Personal Settings page.

Today we updated a few packages to newer versions:

• Yarn 1.5.1 -> 1.9.4
• pyenv 1.2.6 -> 1.2.7
• Python 3.4.8 -> 3.4.9
• Python 3.5.5 -> 3.5.6
• Python 3.6.5 -> 3.6.6

When we launched API v2, we also said that we would deprecate v1 on July 1st, 2018. Not everyone was ready for this, so we’ve extended the date for the final deprecation and shutdown for August 23rd, 2018.

On August 23rd, all access to API v1 will be turned off, and you will only be able to access your CodeShip data via the new API v2.

Please do let us know if you need more time or are having migration issues. We’re here to help, and so far all use cases have been covered by API v2.

The chrome plugin Shipscope has been around for quite some time now and have served lots of users well. Unfortunately, it's relying on API v1 (which is already deprecated as per July 1st) and with the newer browser notifications (Personal Settings -> Notifications) as well as the new flexible notification system, we've decided not to try and update Shipscope

Shipscope was marked as deprecated on the Github Repo on June 21st and it’s data access will be turned off August 17, 2018.

Today we updated a few tools to newer versions:

• ChromeDriver 2.40 -> 2.41
• Firefox 60.0 -> 61.0.1
• Geckodriver 0.20.1 -> 0.21.0

As mentioned earlier, Python 3.3 was EOL'ed last year. Today we fully removed the packages from the CodeShip Basic build image.