---
title: v0.12.0
description: "Auto-generate subdomain deploy steps in CI workflows and stop pinning the seite version so projects always use the latest release."
date: 2026-03-19
tags:
- feature
---

## Subdomain Deploy Steps in Generated Workflows

`seite init` and `seite deploy --setup` now auto-generate deploy steps for subdomain collections. Previously, when a collection had `subdomain` and `deploy_project` configured, only the main site was deployed in CI — users had to manually add the subdomain deploy step.

Now the generated Cloudflare workflow includes steps like:

```yaml
- name: Deploy docs to Cloudflare Pages
  uses: cloudflare/wrangler-action@v3
  with:
    apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
    accountId: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
    command: pages deploy dist-subdomains/docs --project-name my-docs
```

Netlify workflows get equivalent steps with per-collection site ID secrets (`NETLIFY_SITE_ID_DOCS`).

GitHub Pages is unchanged — it doesn't support multi-project deploys.

## Always Install Latest seite in CI

Generated workflows no longer pin `VERSION=x.y.z` in the install command. Instead they use:

```yaml
run: curl -fsSL https://seite.sh/install.sh | sh
```

The install script resolves the latest release via `version.txt`. This means your CI always uses the current seite version without needing to manually update the workflow or run `seite upgrade`.

If you need to pin a specific version, you can still set `VERSION=0.12.0` manually in your workflow.

## Upgrade Path

Run `seite upgrade` to apply both changes to existing projects:

1. **Version unpinning** — removes `VERSION=` from your deploy workflow and netlify.toml
2. **Subdomain steps** — adds missing deploy steps for collections with `deploy_project`

Both are non-destructive: the upgrade regenerates the workflow from your current `seite.toml` configuration.
