Skip to content

Admit the per-line tag segment in the requests source pattern #161

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

Open
iderex wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Admit the per-line tag segment in the requests source pattern #161

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
16 changes: 8 additions & 8 deletions sources/requests.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
{
"account": "Flowfin",
"repository": "jellyfin-plugin-requests",
"slug": "requests",
"stable_tags": "^v?[0-9]+\\.[0-9]+\\.[0-9]+(\\.[0-9]+)?(-stable)?$",
"enabled": true,
"note": "The pattern is the finished-release tagging convention, measured against the longest release history in the set in decisions/channel-model.md: an optional leading v, three or four numeric components, and an optional -stable suffix, which is why the tag rather than the release's pre-release flag decides the channel. It is here so that a finished release enters the catalogue on the day it is tagged and a test build does not. What it selects today is read from the run and from the published catalogue rather than written down here, because a count in this field is wrong again on the next release."
}
{
"account": "Flowfin",
"repository": "jellyfin-plugin-requests",
"slug": "requests",
"stable_tags": "^v?[0-9]+\\.[0-9]+\\.[0-9]+(\\.[0-9]+)?(-jf[0-9]+)?(-stable)?$",
"enabled": true,
"note": "The pattern is the finished-release tagging convention, measured against the longest release history in the set in decisions/channel-model.md: an optional leading v, three or four numeric components, an optional per-server-line segment (-jf12, -jf13, ...) from the one-version-many-lines decision on jellyfin-plugin-requests#110, and an optional -stable suffix, which is why the tag rather than the release's pre-release flag decides the channel. The line segment is here so a -jf12-stable release enters the catalogue on the day it is tagged instead of never; the catalogue still separates lines by targetAbi, the tag segment only names which line a file came from. What it selects today is read from the run and from the published catalogue rather than written down here, because a count in this field is wrong again on the next release."
}
Loading