vt-blog

Today, we are unifying our two primitives – vals and projects – into a single primitive: the val – with the 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 elegant 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 most users, no upgrade 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 upgrading your legacy vals, and integrating with our new API.

April 24, 2025 – Today we announced 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 remaining legacy vals on April 30, 2025.

You can upgrade your your legacy vals early in their Settings by clicking Upgrade. Learn more about how we upgrading legacy vals in our docs.

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

You can view our updated API reference here.

We've released a new version of the Val Town SDK, v0.39.0, which uses these new endpoints.

All v1/vals API routes will become read-only on April 30, 2025. If you rely on writing to those routes, please upgrade before then to our new v2/vals API routes. All deprecated API routes will continue to serve historical legacy val data until further notice.

1. Upgrade your mission-critical vals early
2. Update your Val Town SDK & API usage to /v2 routes
3. All remaining legacy vals will be migrated on April 30, 2025
4. The migration will be complete on May 1, 2025

If you need help or have questions, contact us over email or Discord. We appreciate your help & patience through this migration. There will be good stuff on the other side.