glb_adm/f7_talk
1
0
Fork 0
Code Issues Pull Requests Actions 9 Packages Projects Releases Wiki Activity

UPSTREAM BASELINE: nextcloud/spreed v22.0.12 (без изменений)
Type checking / changes (push) Has been cancelled
Details
Type checking / test (push) Has been cancelled
Details
Type checking / typescript-summary (push) Has been cancelled
Details
Node tests / changes (push) Has been cancelled
Details
Node tests / test (push) Has been cancelled
Details
Node tests / test-summary (push) Has been cancelled
Details

Browse Source 
Источник: https://github.com/nextcloud/spreed/archive/refs/tags/v22.0.12.tar.gz
С этого коммита ветка официального Nextcloud Talk отрезана (решение владельца 2026-07-06).
Все дальнейшие изменения — только наши; версии релизов: 22.0.12-f7.N.
This commit is contained in:
glb_adm
2026-07-06 14:07:50 +00:00
commit 01acfa3b40
1716 changed files with 613013 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/integration/features/integration/outdated-client.feature
+48
View File
@@ -0,0 +1,48 @@
Feature: integration/outdated-client
Background:
Given user "participant1" exists
Scenario: Check if outdated clients correctly receive a 426 error
Given as user "participant1"
# Android
When client "Mozilla/5.0 (Android) Nextcloud-Talk v14.1.1" requests room list with 426 (v4)
Then last response body contains "15.0.0"
When client "Mozilla/5.0 (Android) Nextcloud-Talk v17.0.0" requests room list with 200 (v4)
# iOS
When client "Mozilla/5.0 (iOS) Nextcloud-Talk v14.1.1" requests room list with 426 (v4)
Then last response body contains "15.0.0"
When client "Mozilla/5.0 (iOS) Nextcloud-Talk v17.0.0" requests room list with 200 (v4)
# Desktop
When client "Mozilla/5.0 (Linux) Nextcloud-Talk v0.3.2" requests room list with 426 (v4)
Then last response body contains "1.0.0"
When client "Mozilla/5.0 (Linux) Nextcloud-Talk v1.0.0" requests room list with 200 (v4)
When client "Mozilla/5.0 (Mac) Nextcloud-Talk v0.3.2" requests room list with 426 (v4)
Then last response body contains "1.0.0"
When client "Mozilla/5.0 (Mac) Nextcloud-Talk 1.0.0" requests room list with 200 (v4)
When client "Mozilla/5.0 (Windows) Nextcloud-Talk v0.3.2" requests room list with 426 (v4)
Then last response body contains "1.0.0"
When client "Mozilla/5.0 (Windows) Nextcloud-Talk v1.0.0" requests room list with 200 (v4)
Scenario: Check if outdated clients correctly receive a 426 error with recording consent enabled
Given as user "participant1"
Given recording server is started
And the following "spreed" app config is set
| recording_consent | 2 |
# Android
When client "Mozilla/5.0 (Android) Nextcloud-Talk v17.0.0" requests room list with 426 (v4)
Then last response body contains "18.0.0"
When client "Mozilla/5.0 (Android) Nextcloud-Talk v18.0.0" requests room list with 200 (v4)
# iOS
When client "Mozilla/5.0 (iOS) Nextcloud-Talk v17.0.0" requests room list with 426 (v4)
Then last response body contains "18.0.0"
When client "Mozilla/5.0 (iOS) Nextcloud-Talk v18.0.0" requests room list with 200 (v4)
# Desktop
When client "Mozilla/5.0 (Linux) Nextcloud-Talk v0.8.0" requests room list with 426 (v4)
Then last response body contains "1.0.0"
When client "Mozilla/5.0 (Linux) Nextcloud-Talk v1.0.0" requests room list with 200 (v4)
When client "Mozilla/5.0 (Mac) Nextcloud-Talk v0.8.0" requests room list with 426 (v4)
Then last response body contains "1.0.0"
When client "Mozilla/5.0 (Mac) Nextcloud-Talk v1.0.0" requests room list with 200 (v4)
When client "Mozilla/5.0 (Windows) Nextcloud-Talk v0.8.0" requests room list with 426 (v4)
Then last response body contains "1.0.0"
When client "Mozilla/5.0 (Windows) Nextcloud-Talk v1.0.0" requests room list with 200 (v4)