> For the complete documentation index, see [llms.txt](https://docs.roomiekit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roomiekit.io/open-source-starter/release.md).

# Release checklist

Run the public starter checks before publishing:

```bash
npm run release:verify
```

That command checks for generated/native clutter, removed service references, obvious committed secrets, TypeScript errors, lint errors, and a production web build.

Before creating a public repository, rotate any service credentials that may have existed in private development history, publish from clean history, and run a dependency/license review.

## Public Repo Prep

* Publish from a fresh repository or sanitized history so old `.env`, R2, Supabase, OneSignal, RevenueCat, and Agora values cannot be recovered from commits.
* Keep `.gitattributes` in the public repo and either migrate bundled binaries to Git LFS or ship them as a versioned release asset bundle.
* Verify `web/public` contains only assets you have redistribution rights for, then finish `ASSET_LICENSES.md` and `THIRD_PARTY_NOTICES.md`.
* Keep optional systems disabled by default and document any extra migrations, Edge Functions, webhooks, or provider keys needed to enable them.
* Confirm `git status --short` has no `.env`, `.temp`, `.pnpm-store`, generated web builds, Pods, or copied Capacitor web assets.

## Manual Release Checks

`npm run release:verify` covers local hygiene, secret patterns, typecheck, lint, and build. Before tagging, also run a dependency/license scan, inspect asset licenses, confirm clean history, and do at least one two-browser media smoke test for room voice, TV-head video, theater stream, personal-room video, and direct calls.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.roomiekit.io/open-source-starter/release.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.