---
title: "Public API Now Boarding, Wait for CI, Nixpacks Major Release"
date: 2022-12-19T15:00:00.000+00:00
number: 0112
url: https://railway.com/changelog/2022-12-16-public-api-priority-boarding
---

# Public API Now Boarding, Wait for CI, Nixpacks Major Release

Hope you like quality of life improvements, because this changelog is filled with ‘em! We’re also bringing the Public API into Priority Boarding, introducing a new Wait for CI feature, and releasing a major Nixpacks update!

## Public API Now Open to Priority Boarding

[Image: Create an API token from the Tokens page in Account Settings]

The Railway Public API, which was previously available to teams, is now open to all Priority Boarding users. 

The Public API comes with a number of primitives for managing Railway services and plugins programmatically. Some great integrations are already being built with the API and we’re excited to open the door to more users.

[Read the docs](https://docs.railway.app/reference/public-api) for more info and [join us on Discord](https://discord.com/invite/railway) to talk about your use case. 

We can’t wait to see what you build!

## Wait for CI to Priority Boarding

![Railway can now wait for your CI to run before triggering a new build](https://res.cloudinary.com/railway/image/upload/v1671003153/docs/check-suites.png)

Need your CI to run before triggering a new Railway build? That’s now possible with Wait for CI.

This was first brought to our attention [about a year ago](https://railway.canny.io/feature-requests/p/wait-for-ci-before-deploying) and we’re eager to bring the feature into Priority Boarding. As a first implementation, when `Enable check suites` is toggled in your service settings, Railway will wait for all GitHub Actions to run successfully before triggering a build.

[Let us know](https://discord.com/invite/xAm2w6g) on Discord if this suits your use case. If you need more finely tuned control, let us know what that would look like as we’re actively building out this feature.

## Nixpacks Upgraded to v1.0.2

After more than eight months of minor updates, we’ve finally released a [major version](https://github.com/railwayapp/nixpacks/releases/tag/v1.0.2) for Nixpacks!

Here are the big updates:

- The base now runs on Ubuntu 22 rather than Debian 11
- OpenSSL 1.1 has been upgraded to OpenSSL 3

Please let us know if you encounter any issues. In particular, the upgrade to OpenSSL 3 may have unexpected breaking changes, so be sure to reach out if you need a hand.

We are happy to stamp Nixpacks with that big v1 seal of approval — but there’s much more in store! Stay tuned in the new year when we’ll talk a little more in-depth about our plans to expand Nixpacks.

## Improvements and Fixes

- Added a button to make it easier to copy service and custom domain fields
- Added a new badge to templates in the command palette to provide more context
- Added a notification when switching between environments
- Added a back button to the template deploy flow
- Improved prioritization of elements in the command palette
- Improved the login flow when signing in via email
- Improved readability of long variable values within services and plugins
- Improved consistency of icon sizes across the app
- Improved credit card form to explicitly denote currency
- Improved visibility of team-specific error states in the dashboard
- Fixed a bug with the way team members are displayed, especially on mobile
- Fixed a bug when displaying GitHub-triggered commits with long names
- Fixed a bug with the empty state for variables within a service