---
title: "Sealed Variables Beta, Revamped Cron Jobs Beta, Gitlab Container Registry Support"
date: 2024-09-13
number: 0203
url: https://railway.com/changelog/2024-09-13-sealed-variables
---

# Sealed Variables Beta, Revamped Cron Jobs Beta, Gitlab Container Registry Support

Attention Passengers, this is your friendly Changelog Conductor speaking. 

We’d like to let you know that this is the last week you’ll be able to use the [legacy edge proxy](https://railway.app/changelog/2024-08-02-trust-center#edge-proxy-cutover-progress-) before we flip you over to the new proxy next week. 

As we mentioned previously in Changelogs [#0199](https://railway.app/changelog/2024-08-16-faster-deploys), [#0197](https://railway.app/changelog/2024-08-02-trust-center#edge-proxy-cutover-progress-), [#0195](https://railway.app/changelog/2024-07-19-database-private-networking#new-edge-proxy-migration), [#0190](https://railway.app/changelog/2024-06-14-nyoooom#edge-proxy-rollout-update), and [#0186](https://railway.app/changelog/2024-05-17-new-edge-proxy-beta#introducing-the-new-edge-proxy-(beta)), this will be a seamless transition to the new edge proxy, which will provide near-instant deploy cutovers, new detailed error pages with a traceable Request ID, enhanced DDoS prevention, and many more features that will soon be unlocked. 

No action is needed on your end, we just wanted to let you know. 💫

That’s it for the announcements. Our first stop today is Sealed Variables. 

Mind the gap!

## Sealed Variables Beta

[Video: Sealed Variables is a new feature that provides security-first variable obfuscation ]

As we mentioned [last week](https://railway.app/changelog/2024-09-06-edge-improvements#rbac-is-coming), we’re starting to roll-out some RBAC (role-based access control) features to better serve our customers. 

As a start, today we’re introducing into Beta a security-first feature called [Sealed Variables](https://docs.railway.app/guides/variables#sealed-variables). 

When a variable is sealed, its value is provided to builds and deployments but is never visible in the interface or via the API. 

This is especially handy when you don’t want to leak a private key under any circumstances — something like a Stripe key, for example.

We hope you like this feature. For more information, be sure to [read the docs](https://docs.railway.app/guides/variables#sealed-variables).

After you check out the feature, [join the discussion](https://help.railway.app/feedback/sealed-variables-c1317d54) and let us know how to make it even better.

Next stop, Cron Jobs!

## Revamped Cron Jobs Beta

[Video: Cron Jobs are now more faster and more reliable]

*What do we want? *

Crons that run on-time!

*When do we want them?*

*0 9 * * **

But seriously folks — lately we’ve been fielding a lot of feedback about Crons and the gist is that you need more reliable crons *yesterday*. 

Ok, we’re on it. We went ahead and we made crons faster and more reliable. 

We also now enumerate individual cron executions including providing details on why skips occurred.

We think you’re gonna like the new crons, but don’t take our word for it. To get started, head over to your favorite cron service, go to the service settings, scroll down to `Feature Flags`, and enable `New cron experience`. 

After that, we’d love to get your feedback on the feature. 

Join the conversation [here](https://help.railway.app/feedback/new-cron-experience-a74e2afa) and let us know what you think. Thank you!

Last stop, Gitlab Container Registry!

## Gitlab Container Registry Support

[Video: It’s now possible to deploy docker images as a service from Gitlab Container Registry]

Railway supports deploying images directly from [Docker Hub](https://hub.docker.com/), [GitHub Container Registry (ghcr)](https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-container-registry), [Quay.io](https://quay.io/search), and, as of this week, [GitLab Container Registry](https://docs.gitlab.com/ee/user/packages/container_registry/). 

This feature came directly from a user feature request, so we’ll take the opportunity to remind you to [let us know](https://help.railway.app/feedback) what you’d like Railway to support next. 

If you don’t want to create a new thread, feel free to add something to the [Nits Superthread](https://help.railway.app/feedback/request-tell-us-about-your-nits-on-the-a3c5878e). We’re still working on burning through these issues and it’s not to late to add something to the docket.

Have a great weekend! ✌️

## Fixes and Improvements

- We added a new [Best Practices](https://docs.railway.app/overview/best-practices) page in the docs
- We improved the [Fixing Common Errors](https://docs.railway.app/guides/fixing-common-errors) guide in the docs
- We fixed a bug that prevented some users from publishing templates