We're pleased to announce the addition of a new feature to [DeployHQ](https://www.deployhq.com) Build today - the ability to configure custom build environments in each of your [DeployHQ](https://www.deployhq.com) projects.

Previously, the latest supported version of a given tool (such as PHP or Ruby) was used in all builds, but now if you're using a specific version of one of the supported tools in a build, you'll be able to set up your own custom environment in your project, to be used in any builds run as part of a deployment.

![Language versions](https://blog.deployhq.com/attachment/e479c02b-e4cf-467f-a3a7-50c2ea79c260/AIp-Spd-G.png)

Once you've selected a version, that'll always be used in any future deployments in that project.

![Ruby version](https://blog.deployhq.com/attachment/3d7859bd-f51a-41c6-ab03-834af2a780c8/fmd-EBUp.png)

Anyone already using build commands in a project before today will find they'll continue to use the previous latest versions of our main tools, that were available when the build features were first added to [DeployHQ](https://www.deployhq.com).

Otherwise, you can easily update to the latest supported version in existing project via your **Language Versions** page. Any new projects created in your account will automatically use the latest supported version of each tool.

You'll find the following versions of each tool can now be selected in a custom environment:

- Ruby **2.3** , **2.4** and **2.5**
- PHP **5.6** , **7.0** , **7.1** and **7.2**
- Node **8** and **9**

If you have any questions about this, or any of the other build command features, please don't hesitate to [get in touch](mailto:support@deployhq.com).