Skip to content

docs: document the update-feed branch #33

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
thorstenalpers merged 1 commit into from
Jul 21, 2026
Merged

docs: document the update-feed branch #33

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,6 +42,12 @@ the `build` status check must pass. Every change ships through a PR against
`body_path`).
- **Do not create git tags manually.** `deploy-release.yml` creates the
`v<version>` tag when it publishes.
- The long-lived **`update-feed`** branch holds the AutoUpdater.NET feed: at each
release `deploy-release.yml` regenerates `update-installer.xml` from
`update-template.xml` on it, and the installed app polls that file to detect
new versions. It is a data-only branch — **do not delete it.** Deleting it
breaks the in-app update check and the release workflow (which commits to it).
If it is lost, recreate it from the last `Update for <version>` commit.
- The full release-prep flow (decide SemVer, branch, build/test, bump version,
write release notes, open the PR to `main`) is encoded in the
**`prepare-release`** skill at `.claude/skills/prepare-release/`. Run it via
Expand Down
Loading