• Townie
    AI
  • Blog
  • Docs
  • Pricing
  • We’re hiring!
Log inSign up
stevekrouse

stevekrouse

vt-blog

Steve's fork of the Val Town blog
Remix of valdottown/blog
Public
Like
vt-blog
Home
Code
9
components
12
posts
4
routes
6
styles
1
utils
9
IMAGES.md
README.md
TODOs.md
H
index.ts
Branches
3
Pull requests
Remixes
3
History
Environment variables
Val Town is a collaborative website to build and scale JavaScript apps.
Deploy APIs, crons, & store data – all from the browser, and deployed in milliseconds.
Sign up now
Code
/
posts
/
2025-04-24-upgrading.md
Code
/
posts
/
2025-04-24-upgrading.md
Search
4/21/2025
Viewing readonly version of unifying-vals-and-projects branch: v121
View latest version
2025-04-24-upgrading.md
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 – 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.

Timeline

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.

Upgrading

We will be auto-upgrading all remaining legacy vals on April 30th, 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.

image.png

API Changes

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

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 30th, 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.

What's next

  1. Upgrade your mission-critical vals early
  2. Update your Val Town SDK & API usage to /v2 routes

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.

FeaturesVersion controlCode intelligenceCLI
Use cases
TeamsAI agentsSlackGTM
DocsShowcaseTemplatesNewestTrendingAPI examplesNPM packages
PricingNewsletterBlogAboutCareers
We’re hiring!
Brandhi@val.townStatus
X (Twitter)
Discord community
GitHub discussions
YouTube channel
Bluesky
Open Source Pledge
Terms of usePrivacy policyAbuse contact
© 2025 Val Town, Inc.