SeerrFin Test Manifest

This directory is intentionally separate from the plugin source repository. It is meant for Jellyfin testing only, so the PR branch in SeerrFin stays clean.

What goes here

• manifest.json: the Jellyfin repository manifest for your test instance.
• GitHub Release assets from your fork, for example:
  • Jellyfin.Plugin.SeerrFin_10.11.0.zip

How to use it

1. Build the plugin from your feature branch.
2. Upload the ZIP to a GitHub Release in your fork.
3. Replace the placeholder values in manifest.json:
   • version
   • sourceUrl
   • checksum
   • timestamp
4. Host this manifest.json in a separate repository or as a raw file URL.
5. Add that raw URL as a repository in Jellyfin.

Recommended separation

• Code repo: helitra/SeerrFin
• Test manifest repo: separate repo, for example helitra/SeerrFin-test-manifest
• Test release assets: fork release only

That keeps the later upstream PR free from test-only URLs and release plumbing.

Jellyfin repository URL

Use the raw GitHub URL of the test manifest file, for example:

https://raw.githubusercontent.com/helitra/SeerrFin-test-manifest/main/manifest.json

If you use a different repo name or branch, update the URL accordingly.

Release workflow

See RELEASE_WORKFLOW.md for the exact build → release → checksum → Jellyfin install flow.