| title: | Upgrading vals |
|---|---|
| description: | Vals are being upgraded to support multiple files, folders, and more |
| pubDate: | 2025-04-24T00:00:00.000Z |
| author: | Steve Krouse |
Today, we are unifying our two primitives – vals and projects – into a single primitive: the val – which will have best features of both.
Vals have been known for being simple and lightweight. This upgrade will help us preserve their original spirit, while also supporting more complex code with multiple files, and collaborative workflows with branches and pull requests.
Under the hood, vals are becoming projects. Once the migration is over, we will rename projects to vals. In short: legacy vals → projects → vals.
For 99% of users, no action will be required. We will auto-migrate your vals next week.
For those with mission-critical vals, exotic usage, or extensive API usage, today you can start manually upgrading your legacy vals, and integrating with our new API changes.
April 24, 2025 – Today, we are announcing the changes & API deprecations.
April 30, 2025 – All remaining legacy vals will be auto-upgraded. Deprecated API routes become read-only.
May 1, 2025 – Projects will be renamed to vals across our product and docs.
We will be auto-upgrading all legacy vals on April 30th, 2025. If you would like to upgrade early, you can do so by going to any of your legacy val's Settings and clicking upgrade.