Felitendo a16c2fea5a build: ship separate Jellyfin 10.11 and Jellyfin 12 artifacts ...

The Jellyfin 12 packages target net10.0 only, so one DLL cannot serve
both server generations. A JellyfinTarget switch (jf10/jf12) selects
the framework, the Jellyfin package version and a JF10/JF12 symbol.

Each release produces both artifacts with the same plugin version and
adds two manifest entries, Jellyfin 12 first. Jellyfin filters entries
by targetAbi before its stable sort by version, so manifest order
decides which build a Jellyfin 12 server picks. jprm repo add drops
entries sharing a version, so scripts/update_manifest.py writes them.

The 10.11 build is pinned to the 10.11.0 floor again, so the whole
10.11.x line can install it. CA1873 is relaxed for the .NET 10
analyzers, and CI builds both targets.

2026-09-15 15:45:00 +02:00

..

build.yaml

build: ship separate Jellyfin 10.11 and Jellyfin 12 artifacts

2026-09-15 15:45:00 +02:00

command-dispatch.yaml

init

2024-02-10 18:29:38 -07:00

command-rebase.yaml

init

2024-02-10 18:29:38 -07:00

publish.yaml

build: ship separate Jellyfin 10.11 and Jellyfin 12 artifacts

2026-09-15 15:45:00 +02:00

release-notes.yaml

fix: pass changelog body via env+notes-file in release-notes workflow

2026-05-08 11:55:26 +02:00

scan-codeql.yaml

Update scan-codeql.yaml

2025-09-25 09:46:34 +02:00

sync-labels.yaml

init

2024-02-10 18:29:38 -07:00

test.yaml

init

2024-02-10 18:29:38 -07:00