feat(help): move links and updates to Gitea and add Share #57

Open
james.maes wants to merge 1 commits from feat/gitea-links-and-share into main
pull from: feat/gitea-links-and-share
Owner

Closes #56

What changes

  • Links: AppIdentity.Info.RepositoryUrl is the Gitea repository. The Help menu, About dialog, README download links and user guide follow it. Credits for other people's projects keep their own addresses.
  • Updates: the update check reads the Gitea releases through Velopack's Gitea source. ReleaseUpdateService (core, fully tested) implements AppKit's IUpdateService; GiteaReleaseUpdater (app) is the pass-through.
  • Help → Share MarkdownViewr: opens a ready-to-send invitation email (mailto: with subject and body, no recipient). Falls back to copying the invitation to the clipboard.
  • Help → Community support opens the issue list; View on GitHub becomes Project page.
  • ADR-0007, threat model rows for the update source and the invitation, user guide section.

Checks run

  • All local gates: locked restore, zero-warning build, format, 696 core tests at 100% line coverage, 30 adapter tests, fuzz.
  • Velopack's Gitea source against the live repository, without credentials: returns the 1.0.3 feed for stable and the 1.0.3-beta.1 feed for dev.
  • Every link form the app uses answered by the Gitea server (license, issues, latest release, latest installer, user guide).

Not run

  • The Desktop tests, and a real update from an installed copy.
  • The installed-update acceptance harness still exercises AppKit's GitHub service against a local fixture; porting it is recorded in ADR-0007.

To know before merging

Copies installed from 1.0.3 or earlier look at GitHub for updates and will not find a release published only on Gitea.

AI assistance: written with Claude Fable 5.2.

🤖 Generated with Claude Code

Closes #56 ## What changes - **Links**: `AppIdentity.Info.RepositoryUrl` is the Gitea repository. The Help menu, About dialog, README download links and user guide follow it. Credits for other people's projects keep their own addresses. - **Updates**: the update check reads the Gitea releases through Velopack's Gitea source. `ReleaseUpdateService` (core, fully tested) implements AppKit's `IUpdateService`; `GiteaReleaseUpdater` (app) is the pass-through. - **Help → Share MarkdownViewr**: opens a ready-to-send invitation email (`mailto:` with subject and body, no recipient). Falls back to copying the invitation to the clipboard. - **Help → Community support** opens the issue list; **View on GitHub** becomes **Project page**. - ADR-0007, threat model rows for the update source and the invitation, user guide section. ## Checks run - All local gates: locked restore, zero-warning build, format, 696 core tests at 100% line coverage, 30 adapter tests, fuzz. - Velopack's Gitea source against the live repository, without credentials: returns the 1.0.3 feed for `stable` and the 1.0.3-beta.1 feed for `dev`. - Every link form the app uses answered by the Gitea server (license, issues, latest release, latest installer, user guide). ## Not run - The `Desktop` tests, and a real update from an installed copy. - The installed-update acceptance harness still exercises AppKit's GitHub service against a local fixture; porting it is recorded in ADR-0007. ## To know before merging Copies installed from 1.0.3 or earlier look at GitHub for updates and will not find a release published only on Gitea. AI assistance: written with Claude Fable 5.2. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
james.maes added 1 commit 2026-11-11 00:52:17 +00:00
feat(help): move links and updates to Gitea and add Share
node / node (push) Successful in 33s
build / scripts (push) Successful in 33s
windows / windows (push) Successful in 1m51s
build / windows (push) Successful in 1m51s
ca1fb827cd
The app's repository address is now the Gitea repository, and every
page the Help menu, the About dialog and the README open is derived
from it. Help > Community support opens the issue list, since Gitea
has no discussions.

The update check reads the Gitea releases. The decisions live in a
core service that implements AppKit's update interface, so AppKit's
coordinator and dialogs are used unchanged; the app supplies a
pass-through to Velopack's Gitea release source.

Help > Share MarkdownViewr starts an email with an invitation already
written: the installer link, the release page, the user guide and
where to report problems. Without an email program the invitation is
copied to the clipboard.

ADR-0007 records the move and what it means for installed copies.

Closes #56

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Signed-off-by: James Maes <james@kof22.com>
All checks were successful
node / node (push) Successful in 33s
build / scripts (push) Successful in 33s
windows / windows (push) Successful in 1m51s
build / windows (push) Successful in 1m51s
This pull request has changes conflicting with the target branch.
  • docs/security/threat-model.md
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin feat/gitea-links-and-share:feat/gitea-links-and-share
git checkout feat/gitea-links-and-share
Sign in to join this conversation.