The release was held for #498; while it was held, both #498 and #67 merged, so the v26.11.0 version-table row written in #501 was already stale — it led with the media-scanner work and didn't mention either feature.
#498 leads the row because it flips a default: QsvPreferNativeDecoder ships ON, so every existing QSV profile changes decode behavior on upgrade. That's the thing an operator reading the version table needs to see first, not a fixes-list entry.
Release range is now 83 commits across v26.10.0..36499a96, and it carries a proper dual-provider migration (Add_FFmpegProfile_QsvPreferNativeDecoder, Sqlite + MySql).
No independent review requested: single-line docs change, no server-state effect (stated exemption per the review skip rubric).
Docs-only, one line. Follow-on to #501.
The release was held for #498; while it was held, both #498 and #67 merged, so the `v26.11.0` version-table row written in #501 was already stale — it led with the media-scanner work and didn't mention either feature.
**#498 leads the row** because it flips a default: `QsvPreferNativeDecoder` ships **ON**, so every existing QSV profile changes decode behavior on upgrade. That's the thing an operator reading the version table needs to see first, not a fixes-list entry.
Release range is now **83 commits** across `v26.10.0..36499a96`, and it carries a proper dual-provider migration (`Add_FFmpegProfile_QsvPreferNativeDecoder`, Sqlite + MySql).
No independent review requested: single-line docs change, no server-state effect (stated exemption per the review skip rubric).
The release range grew after the host-correction PR landed: #67 and #498 both
merged into main. #498 in particular flips a default (QsvPreferNativeDecoder is
ON), so it leads the row rather than sitting in a fixes list.
timothy
merged commit 601d855b25 into main2026-07-20 22:22:05 +02:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Docs-only, one line. Follow-on to #501.
The release was held for #498; while it was held, both #498 and #67 merged, so the
v26.11.0version-table row written in #501 was already stale — it led with the media-scanner work and didn't mention either feature.#498 leads the row because it flips a default:
QsvPreferNativeDecoderships ON, so every existing QSV profile changes decode behavior on upgrade. That's the thing an operator reading the version table needs to see first, not a fixes-list entry.Release range is now 83 commits across
v26.10.0..36499a96, and it carries a proper dual-provider migration (Add_FFmpegProfile_QsvPreferNativeDecoder, Sqlite + MySql).No independent review requested: single-line docs change, no server-state effect (stated exemption per the review skip rubric).