Skip to content

Flared 0.1.1

Choose a tag to compare

View all tags
@PGHQdev PGHQdev released this 14 Oct 03:08
· 44 commits to release since this release
v0.1.1
ab5d653

Deploy

  • Deploy on Cloudflare asks only for SETUP_SECRET: choose any value of at least 16 characters and type it once at /setup.
  • APP_ORIGIN is optional. Without it, the address where you do the setup becomes the app address. Set it to move the app; see origin.md.
  • AUTH_SECRET is optional. Without it, the Worker makes its own key and keeps it in the identity database. If your copy has AUTH_SECRET, keep it: without it, everyone must sign in again.

Update notices

  • The owner can turn on update checks in the setup wizard or in Settings → Updates. They are off by default.
  • While they are on, the app reads https://flared.page/releases/latest.json once a day. The request has no cookie, no version, and no data about your installation.
  • A newer release shows a notice with its summary, its database changes, and the upgrade steps.

Upgrade workflow

  • deploy/flared-upgrade.yml opens a pull request in your repository for each release, or an issue when you must act. Add it once as .github/workflows/flared-upgrade.yml; Settings → Updates opens GitHub with the file filled in.
  • When GitHub does not let the workflow open pull requests, the issue links the pull request for you to open and the setting that allows it.
  • Auto mode (FLARED_AUTO_UPGRADE=true, off by default) merges a clean upgrade unless a release in it is marked breaking.
  • See the upgrade guide. A copy made from v0.1.0 needs the workflow file once; a copy made before 13 October 2026 needs the first upgrade by hand.

Fixes

  • Copy fields, such as the MCP server URL, show the whole value.

Database changes

  • packages/data/migrations/identity/0018_update_check.sql adds the update_check table.
  • packages/data/migrations/identity/0019_installation_key.sql adds the installation_key table.

bun run deploy applies them before it deploys the Worker.

Assets 2
Loading