15 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
Thore CimbalandClaude Sonnet 5	59f9c81ef8	ci: use lockfile install instead of layered.sh, fix always-green gate ... layered.sh clones a branch-matching upstream matrix-js-sdk - on this fork that would override the deliberately pinned js-sdk from pnpm-lock.yaml (issue #12) with upstream develop, and it also needs jq which the node:20 job container lacks (the actual CI failure). Plain frozen-lockfile install matches the production docker build. Also replace the contains(needs.*.result, ...) gate check with explicit per-job checks: the object-filter syntax evaluated wrongly on Gitea/act, letting build-complete report success while build_ew had failed. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-07-30 22:28:32 +02:00
Thore CimbalandClaude Sonnet 5	6a8a2bb1a9	ci: map runs-on to actual runner labels, trim jobs the runner can't serve ... Root cause found for jobs never starting: runs were created all along (visible in the Actions UI), but every job requested ubuntu-24.04 while builder-1 only offers ubuntu-latest, linux-build and win-wine - a label mismatch means jobs queue forever, invisible via the /actions/tasks API which only lists picked-up jobs. Mapped build/prepare/gate jobs to ubuntu-latest and the Linux desktop build to linux-build (electronuserland/builder image, amd64/static only - the only variant buildable on the single x86 runner). Removed jobs the runner cannot serve instead of letting them starve the queue: web+desktop playwright tests (need Docker-in-job and display setup, tracked as follow-up in issue #2) and the native-Windows desktop build (workflow assumes signtool/MSVC/PowerShell; the win-wine label awaits a dedicated wine-based workflow). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-07-30 22:23:00 +02:00
Thore Cimbal	214fd5b70a	ci: test push after git-hook resync	2026-07-30 22:14:03 +02:00
Thore CimbalandClaude Sonnet 5	8fb32d9360	ci: remove unused workflow_call trigger (Gitea Actions bug go-gitea/gitea#33238) ... push + workflow_call in the same on: block doesn't reliably fire push events on Gitea Actions 1.27 (reproducible upstream, closed as "not planned" - https://github.com/go-gitea/gitea/issues/33238). Nothing in this repo invokes build-and-test.yaml via workflow_call anymore after the workflow cleanup, so removing the trigger is a safe, targeted fix rather than a workaround. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-07-30 19:39:39 +02:00
Thore Cimbal	b24ce732dc	ci: add trigger-test note to force a real push event	2026-07-30 19:32:34 +02:00
Thore Cimbal	163504efc6	ci: trigger first Actions run now that Actions is enabled for this repo	2026-07-30 19:25:24 +02:00
Thore CimbalandClaude Sonnet 5	170d6c3538	ci: reduce workflows to fork-relevant CI, fix upstream checkouts (Issue #2) ... Removed ~37 workflow files that are unmodified upstream tooling this fork doesn't use (Netlify, SonarCloud, Localazy, release-drafter/backport, GitHub issue-triage bots, npm-publish, Cloudflare Pages deploy, Docker push to ghcr.io/element-hq). Enabling Actions for this repo would have activated all of them simultaneously against a single-capacity shared runner - most would just fail loudly and starve the one job slot shared with other repos. Kept build-and-test.yaml (the actual comprehensive build+test+desktop workflow) and its build_desktop_*.yaml sub-workflows. Fixed: push trigger now targets `main` (was `staging`/`master`, neither of which exist here - push events never fired at all before), 4 checkout steps now check out this fork instead of element-hq/element-web, and removed the macOS desktop build job since the registered runner (builder-1) has no macOS label and would queue forever instead of failing cleanly. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-07-30 19:10:00 +02:00
Thore Cimbal	60f2cda962	docs: add axion1337-fork.md documenting fork-specific changes vs upstream	2026-07-30 00:27:26 +02:00
Thore Cimbal	6a628533c2	feat: client-side ClamAV scanning for encrypted rooms (Issue #19) ... Synapse's own check_media_file_for_spam module can never see E2EE attachment content - only the client ever holds the decryption key. Adds two hooks that call a self-hosted scan service (https://axion1337.chat/_scan, deployed separately in the gitops repo): - DecryptFile.ts: scans every decrypted attachment (image/audio/video/ file all funnel through this one function via MediaEventHelper) before returning it as a Blob. - ContentMessages.ts: scans plaintext before encryption/upload in uploadFile(), the shared function behind all attachment uploads (main file, thumbnails, voice messages), regardless of room encryption state. New ContentScanRejectedError surfaces through the existing error- rendering paths (MediaProcessingError, upload failure dialog) using the same pattern as DecryptError/DownloadError/UploadFailedError. Live-tested: EICAR blocked pre-upload in encrypted rooms and DMs; receive-side hook also blocks EICAR sent by an unpatched client (app.element.io), confirming it isn't just self-protection for our own uploads. Fails open on scanner errors so an outage can't block all uploads/downloads.	2026-07-29 19:29:03 +02:00
Thore Cimbal	05900602c6	fix: restore executable bit on remaining desktop/CI scripts ... The earlier script-permission fix (5e3254d) only covered scripts invoked by apps/web's own Dockerfile/CI at the time. Found 9 more non-executable scripts (644 instead of 755) while building the Electron desktop app via apps/desktop/dockerbuild - same root cause, different invocation paths.	2026-07-29 19:11:34 +02:00
Thore Cimbal	7839b56a65	fix: pin matrix-js-sdk to a working commit, use our own Element Call fork ... The floating github:matrix-org/matrix-js-sdk#develop reference was resolved to a stale commit missing src/oidc/authorize.ts (breaking the webpack build). Investigated moving to the current develop HEAD instead (191908da) - turned out to be worse, not better: that commit renamed the entire src/oidc/ module to src/oauth/ with a materially different API (generateOidcAuthorizationUrl/completeAuthorizationCodeGrant/OidcError don't exist under those names anymore). Rather than porting our OIDC login code to the new API sight-unseen, pinned to d19cb751 - the last develop commit before that rename, verified to have both the file at the expected path and the exact exports apps/web imports. Also switched the Element Call embedded widget dependency from upstream's @element-hq/element-call-embedded to our own published fork (@sorb/threadnet-call-embedded@0.19.2-threadnet.5) - a full rebuild was otherwise silently bundling the unmodified upstream widget, discarding every Element Call customization (Video-tab quality settings, German translations, codec list fix).	2026-07-28 23:36:53 +02:00
Thore Cimbal	5e3254d8a8	fix: restore executable bit on scripts invoked directly by Dockerfile/CI ... apps/web/Dockerfile invokes scripts/docker-link-repos.sh and scripts/docker-package.sh directly (no bash prefix) - without +x this fails immediately on any fresh clone/full rebuild. The same bug also affects fetchdep.sh, get-version-from-git.sh, layered.sh, normalize-version.sh, and playwright-common/playwright-screenshots.sh, all invoked directly the same way by this repo's own GitHub Actions workflows (build.yml, tests.yml, static_analysis.yaml, docs.yml) - so this was also silently breaking CI, not just Docker builds.	2026-07-28 23:26:27 +02:00
sorB	9c7ece2241	feat: call participants orientation vertical vertical	2026-05-10 21:09:19 +02:00
sorB	3da363517f	feat: show call participants in room list (Discord-style) Test	2026-05-10 14:25:35 +02:00
sorb	b797925316	Initial commit	2026-05-10 11:31:35 +00:00