
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, but limited to a single file. This upgrade will help us preserve the clean and intuitive spirit of our platform, while also supporting more complex code with multiple files, and collaborative workflows with branches and pull requests.
Under the hood, legacy 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 is required. We will auto-migrate your vals next week.
For those with mission-critical vals or extensive API usage, today you can start manually upgrading your legacy vals, and integrating with our new API.
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, go to your legacy val's Settings and click upgrade.
Today we are introducing the following API routes:
GET /v2/vals/{val_id} DELETE /v2/vals/{val_id} GET /v2/vals POST /v2/vals GET /v2/vals/{val_id}/branches/{branch_id} DELETE /v2/vals/{val_id}/branches/{branch_id} GET /v2/vals/{val_id}/branches POST /v2/vals/{val_id}/branches GET /v2/vals/{val_id}/files POST /v2/vals/{val_id}/files DELETE /v2/vals/{val_id}/files PUT /v2/vals/{val_id}/files GET /v2/vals/{val_id}/files/content GET /v2/alias/handle/{val_name}
We deprecated the following API routes:
* /v1/vals/* GET /v1/alias/handle/{val_name} GET /v1/alias/projects/{username}/{project_name} GET /v1/me/comments GET /v1/me/references GET /v1/me/likes
The Val Town SDK supports these changes in v0.39.0
.
All v1/vals
routes will become read-only on April 30th, 2025. If you rely on writing to those routes, please upgrade to our new v2/vals
routes. All deprecate API routes will continue to serve historical legacy val data.