summaryrefslogtreecommitdiffhomepage
AgeCommit message (Collapse)AuthorFilesLines
2026-04-21Set github runner xcode versionupdate-formattingJon Petersson1-0/+2
2026-04-21Merge branch 'notify-app-ios-on-successful-nightly-test-runs-ios-1575'Jon Petersson2-16/+4
2026-04-21Correct `successful` to `success` Daneo Van Overloop1-1/+4
According to [this documentation][1], I should've written `success` instead of `successful`, and this is also double-checked by querying the API: ```sh curl -SsfL -H @headers $GITHUB_API | jq '{ state, conclusion }' { "state": null, "conclusion": "success" } ``` [1]: https://archive.is/4IM5j#check-statuses-and-conclusions
2026-04-21Remove duplicate iOS E2E tests-notificationsDaneo Van Overloop1-15/+0
After testing and observing, we'll now use the `workflow_run` method of observing a workflow's result to trigger failure notifications when needed. **Impact**: Right now we receive a **duplicate** notification if the nightly run fails due to failing tests (as described in 9d89d7316104b2cbd158f78d94bdf824d2274d69). Removing this delegates the notification responsibility entirely to the `ios-end-to-end-nightly-monitor`-workflow, which also offers observability when the run is cancelled, amongst [other][1] possible reasons. [1]: https://archive.is/4IM5j#check-statuses-and-conclusions
2026-04-20Merge branch 'minor-refactor'David Lönnhager18-183/+152
2026-04-20Replace some cfg!() chains with cfg_select!()David Lönnhager10-99/+73
2026-04-20Use if-let guards in some match expressionsDavid Lönnhager8-84/+79
2026-04-20Merge branch 'update-rust-setup'David Lönnhager2-5/+12
2026-04-20Default to host platform in setup-rust-post-checkoutDavid Lönnhager1-4/+11
2026-04-20Add correct Windows targets in setup-rust scriptDavid Lönnhager1-1/+1
2026-04-20Merge branch 'win-set-tun-provider-mtu'David Lönnhager2-2/+1
2026-04-20Set MTU in Windows tun providerDavid Lönnhager2-2/+1
2026-04-20Merge branch 'rename-testscriptsbuild-to-testscriptsbuild-scripts-des-1792'Markus Pettersson6-10/+10
2026-04-20Rename `scripts/build` to `scripts/build-scripts`Markus Pettersson6-10/+10
2026-04-20Merge branch 'remove-golang-from-build-container'Markus Pettersson1-14/+0
2026-04-20Remove Golang from build container DockerfileMarkus Pettersson1-14/+0
Update base Dockerfile to remove Golang, since all app version built by this container no longer depend on wireguard-go.
2026-04-20Merge branch 'notify-app-ios-on-successful-nightly-test-runs-ios-1575'Emīls1-0/+28
2026-04-20Send a Slack notification on a non-successful iOS E2E workflowDaneo Van Overloop1-0/+28
This commit introduces a notification on any case of a `completed` but unsuccessful workflow (i.e. where the conclusion is not `success`). **Rationale**: We currently send a notification if the E2E tests run and fail. Due to runner issues some scheduled nightly runs never get executed. As we only get notified of failing runs, we assume that "No news is good news", but that is not necessarily true. According to [this GitHub documentation][1] we should be able to monitor whether the iOS E2E test workflow is completed, which fits wanting to be informed about _both_ failed tests and scheduled runs, regardless of the reason. **How to test**: ~We should be able to execute the workflow using this PR/branch.~ According to the [documentation][2] this will only run on the `default` branch: > This event will only trigger a workflow run if the workflow file > exists on the default branch. **Technical details**: - [Workflow_run][3] has 3 `action types`: `requested`, `in_progress` and `completed`. - The `workflow_run` payload is documented [here][4]. **Note**: As I did not delete the original notification in `ios-end-to-end-tests-nightly.yml`, failed runs will notify us twice right now. I'd propose to remove that notification _after_ we've observed this notification to work consistently. **Caveat**: I did come across https://github.com/orgs/community/discussions/21090, but given the amount of time that has passed, I'm curious to see if that issue has been resolved in the meantime. [1]: https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows#running-a-workflow-based-on-the-conclusion-of-another-workflow [2]: https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows#workflow_run [3]: https://docs.github.com/en/webhooks/webhook-events-and-payloads?actionType=completed#workflow_run [4]: https://docs.github.com/en/rest/actions/workflow-runs?apiVersion=2026-03-10#get-a-workflow-run
2026-04-20Merge branch 'fix-split-tun-clear'David Lönnhager3-12/+11
2026-04-20Update changelogDavid Lönnhager1-0/+3
2026-04-20Fix 'mullvad split-tunnel clear' getting stuckDavid Lönnhager1-7/+3
Reading from mullvad-exclude's `cgroup.procs` immediately after moving a process to its parent causes it to be moved back to the mullvad-exclude cgroup. This causes 'mullvad split-tunnel clear' to never complete.
2026-04-20Rename incorrect references to cgroup2David Lönnhager1-5/+5
2026-04-20Merge branch 'add-monospace-font-droid-2499'Kalle Lindström5-18/+76
2026-04-20Add monospace font when showing account numberKalle Lindström5-18/+76
2026-04-17Merge branch 'fix-ram-limits-for-reproducible-build-check-droid-2634'Albin3-10/+12
2026-04-17Add memory limit to nix buildsAlbin1-0/+2
This is done the same way as for the other builds in the Android reproducible builds workflow.
2026-04-17Move workflow memory limit to GRADLE_OPTSAlbin2-7/+4
2026-04-17Add support for setting container GRADLE_OPTSAlbin1-0/+2
2026-04-17Fix broken reproducible diff commandAlbin1-3/+4
2026-04-17Merge branch 'add-ubuntu2604'Markus Pettersson2-4/+9
2026-04-17Fix test-runner setup script failing if run multiple timesMarkus Pettersson1-2/+7
2026-04-17Add Ubuntu 26.04 VM for end-to-end testsMarkus Pettersson1-2/+2
2026-04-17Merge remote-tracking branch 'origin/fix-hanging-version-check'David Lönnhager1-1/+6
2026-04-17Fix GetVersionInfo RPC hanging indefinitely in dev buildsDavid Lönnhager1-1/+6
In dev builds where MULLVAD_ENABLE_DEV_UPDATES is not set, the VersionUpdaterInner::run method was silently draining the refresh channel without ever sending a response via update_sender. This caused GetVersionInfo RPCs to hang indefinitely. Fix by sending the dev version cache immediately on startup and on every refresh request.
2026-04-17Assign ownership for sigstore filesDavid Lönnhager1-0/+3
2026-04-17Merge branch 'upgrade-rust-1.95'David Lönnhager21-52/+53
2026-04-17Update android-container-image.txtMullvad build server1-1/+1
2026-04-17Add container signature for mullvadvpn-app-build-android:6103dbf051Mullvad build server2-0/+9
2026-04-17Point Android Dockerfile to new imageMullvad build server1-1/+1
2026-04-17Update linux-container-image.txtMullvad build server1-1/+1
2026-04-17Add container signature for mullvadvpn-app-build:09b5e4e744Mullvad build server2-0/+0
2026-04-17Update nix flakeDavid Lönnhager1-15/+15
2026-04-17Fix clippy lints after 1.95 updateDavid Lönnhager10-31/+23
2026-04-17Upgrade Rust to 1.95.0David Lönnhager3-3/+3
2026-04-17Merge branch 'add-osv-scanner-ignore-for-bc'David Göransson1-0/+6
2026-04-17Add ignore for GHSA-wg6q-6289-32hpDavid Göransson1-0/+6
2026-04-17Merge branch 'create-daita-e2e-test-droid-2366'Jonatan Rhodin6-3/+69
2026-04-17Add Daita E2E testKalle Lindström6-3/+69
2026-04-17Merge branch 'implement-settings-migration-ios-1548'Emīls8-6/+626
2026-04-17Implement multihop settings migrationMojgan8-6/+626