Skip to content

(fix) apply Library date format, fix 'dateadded' filter #4048

(fix) apply Library date format, fix 'dateadded' filter

(fix) apply Library date format, fix 'dateadded' filter #4048

Triggered via pull request May 5, 2026 22:49
Status Success
Total duration 1h 17m 22s
Artifacts 10

develop.yml

on: pull_request
Check if build should be stopped
3s
Check if build should be stopped
git  /  block-fixup
19s
git / block-fixup
Matrix: build / Flatpak
Matrix: build / build
Matrix: checks / build-checks
pre-commit  /  Detecting code style issues
2m 54s
pre-commit / Detecting code style issues
build  /  Update manifest file on download server
39s
build / Update manifest file on download server
Ready to merge
4s
Ready to merge
Fit to window
Zoom out
Zoom in

Annotations

21 warnings
pre-commit / Detecting code style issues
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build / Ubuntu 24.04
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@0.3.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build / macOS 15 arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@0.3.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build / Windows 11 ARM64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/msvc-problem-matcher@0.3.0, ilammy/msvc-dev-cmd@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build / Windows 2022 x64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/msvc-problem-matcher@0.3.0, ilammy/msvc-dev-cmd@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build / Android 15 arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@0.3.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build / Android 15 arm64: build/android-build/src/org/mixxx/UsbPermission.java#L35
[deprecation] <T>getParcelableExtra(String) in Intent has been deprecated
checks / clazy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@0.3.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
checks / clazy: src/qml/qmlconfigproxy.cpp#L234
Missing emit keyword on signal call mixxx::qml::QmlConfigProxy::controlLoopDefaultColorIndexChanged [-Wclazy-incorrect-emit]
checks / clazy: src/qml/qmlconfigproxy.cpp#L233
Missing emit keyword on signal call mixxx::qml::QmlConfigProxy::controlHotcueDefaultColorIndexChanged [-Wclazy-incorrect-emit]
checks / clazy: src/qml/qmlconfigproxy.cpp#L232
Missing emit keyword on signal call mixxx::qml::QmlConfigProxy::libraryRowHeightChanged [-Wclazy-incorrect-emit]
checks / clazy: src/qml/qmlconfigproxy.cpp#L227
Missing emit keyword on signal call mixxx::qml::QmlConfigProxy::libraryBpmColumnPrecisionChanged [-Wclazy-incorrect-emit]
checks / clazy: src/qml/qmlconfigproxy.cpp#L222
Missing emit keyword on signal call mixxx::qml::QmlConfigProxy::libraryEnableSearchHistoryShortcutsChanged [-Wclazy-incorrect-emit]
checks / clazy: src/qml/qmlconfigproxy.cpp#L217
Missing emit keyword on signal call mixxx::qml::QmlConfigProxy::libraryEnableSearchCompletionsChanged [-Wclazy-incorrect-emit]
checks / clazy: src/qml/qmlconfigproxy.cpp#L216
Missing emit keyword on signal call mixxx::qml::QmlConfigProxy::libraryHideMenuBarChanged [-Wclazy-incorrect-emit]
checks / clazy: src/qml/qmlconfigproxy.cpp#L211
Missing emit keyword on signal call mixxx::qml::QmlConfigProxy::libraryInhibitScreensaverChanged [-Wclazy-incorrect-emit]
checks / clazy: src/qml/qmlconfigproxy.cpp#L206
Missing emit keyword on signal call mixxx::qml::QmlConfigProxy::libraryTooltipsChanged [-Wclazy-incorrect-emit]
checks / clazy: src/qml/qmlconfigproxy.cpp#L173
Missing emit keyword on signal call mixxx::qml::QmlConfigProxy::multiSamplingLevelChanged [-Wclazy-incorrect-emit]
build / macOS 15 x64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@0.3.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
checks / clang-tidy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@0.3.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
checks / coverage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ammaraskar/gcc-problem-matcher@0.3.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
Mixxx-2.7-alpha-253-gc60f45e661-aarch64.Debug.flatpak Expired
239 MB
sha256:614c537fbc3d12b193efaed02a78cfaefcf4961c79b63e60b3ed86a42a4c3b39
Mixxx-2.7-alpha-253-gc60f45e661-aarch64.flatpak Expired
17.7 MB
sha256:9bf04fb544a15bc489f1ff30ead9e88a7383e955b63fbee9d9ed42dae253243c
Mixxx-2.7-alpha-253-gc60f45e661-x86_64.Debug.flatpak Expired
245 MB
sha256:08c908941125d8416d588a4117eb584a2cbb3adbb9344ed6f9edf61b7c1f62e1
Mixxx-2.7-alpha-253-gc60f45e661-x86_64.flatpak Expired
18.5 MB
sha256:b1bdd3bf2996c1008c19d9cc690b149fe86cf2aca33cd8497668b3bb1de02d87
android-build-release-signed.apk Expired
263 MB
sha256:23d2563bacf788d66e28b4684199cbbb9f6d441201881ceaf938cba0675b86af
mixxx-2.7-alpha-253-gc60f45e661-amd64.msi Expired
99.1 MB
sha256:61fc765aaf4a91df3421170e2b74813420d2f614b413ccaec82fa8e9893be8bf
mixxx-2.7-alpha-253-gc60f45e661-arm64.dmg Expired
66.3 MB
sha256:6518af00d671fea92c0a5c4b7ad7f756272fa93d3743306db3ec2d40c792ec4c
mixxx-2.7-alpha-253-gc60f45e661-arm64.msi Expired
93.9 MB
sha256:46c7de54a083e0ca6d8f5d53de863aff3b84868b7e6f6f71ce17f875b9198d3e
mixxx-2.7-alpha-253-gc60f45e661-x86_64.deb Expired
22.8 MB
sha256:966d1ee7653043830e53d6f3f3cf7f87c38c294e8053dd77e40bb6c2483064a7
mixxx-2.7-alpha-253-gc60f45e661-x86_64.dmg Expired
62.1 MB
sha256:c2e678f5212d933e83af8b1c63f767781cde9d7b448080409fe07b5b6c2a8d3b