> ## Documentation Index
> Fetch the complete documentation index at: https://docs.feedbackloop.page/llms.txt
> Use this file to discover all available pages before exploring further.

# In-app release notes

> Choose React, Tauri or the anonymous HTTP API for your release notes integration.

Publish an update once in Feedback Loop and show it inside your app. `@feedbackloop/react@0.1.0` is [available on npm](https://www.npmjs.com/package/@feedbackloop/react) under MIT. The anonymous API is live at `feedbackloop.page`; no API key, account sign-in or Convex client is required.

Open your project's **Release notes → Add to app** page for its public project ID. Choose a guide:

* [React](https://docs.feedbackloop.page/integrations/release-notes/react.md): install the reader and scoped stylesheet in a React 19 app.
* [Tauri](https://docs.feedbackloop.page/integrations/release-notes/tauri.md): mount native windows and Settings with an app-owned updater in a React 19/Tauri 2 app.
* [HTTP API](https://docs.feedbackloop.page/integrations/release-notes/http-api.md): fetch the wire contract from any client and provide your own rendering.

## Prepare a release

Write your note and optionally enter an **App version**, such as `1.2.3`. Use a complete semantic version; prerelease and build suffixes such as `1.2.3-beta.1+desktop.7` are preserved. Each project can have one published note per exact version. Drafts can share a version. Unpublishing or deleting a note frees that version for another publication.

Leave the version blank for a general update. Unversioned notes remain in the full history. Changing content or its app version restores Draft; choose **Publish** when it is ready. Version numbers select release notes; your app's updater decides which software update a customer can install.

## React

The [React guide](https://docs.feedbackloop.page/integrations/release-notes/react.md) covers props, exact versions, themes, Markdown, loading, errors and saved copies.

## Tauri 2

The [Tauri guide](https://docs.feedbackloop.page/integrations/release-notes/tauri.md) contains complete installation, root wiring, Settings and updater setup.

### Consumer-owned updater

The [typed updater contract and complete adapter](https://docs.feedbackloop.page/integrations/release-notes/tauri.md#consumer-owned-updater) keep persistence, native update handles, installation and relaunch in your app.

### Existing secondary settings window

Use the [secondary Settings setup](https://docs.feedbackloop.page/integrations/release-notes/tauri.md#existing-secondary-settings-window) when main stays hidden and an existing window owns the Settings UI.

### Native capabilities

Copy the [exact local capabilities](https://docs.feedbackloop.page/integrations/release-notes/tauri.md#native-capabilities) for main, SDK children and optional existing Settings windows.

## Verification before release

Verify your own published project, exact native version and offline recovery. Before shipping a desktop binary, complete signed installer/relaunch acceptance for each supported OS. See the [Tauri release checks](https://docs.feedbackloop.page/integrations/release-notes/tauri.md#recovery-and-release-checks); SDK fixture CI is separate from consumer installer acceptance.

## Anonymous HTTP API

The [HTTP API guide](https://docs.feedbackloop.page/integrations/release-notes/http-api.md) covers full response fields, publication-order pagination, exact versions, errors, CORS and managed images.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.