aboutsummaryrefslogtreecommitdiff
path: root/Dockerfile.windows
Commit message (Collapse)AuthorAgeFilesLines
* build: prepare v0.18.5.1selsta2026-07-031-2/+2
|
* Merge pull request #4614tobtoht2026-06-301-11/+2
|\ | | | | | | | | | | 5564db6 Dockerfiles: pin Qt to a commit hash (Thomas) ACKs: selsta
| * Dockerfiles: pin Qt to a commit hashThomas2026-06-231-11/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Qt was cloned with -b ${QT_VERSION} --depth 1 but, unlike every other dependency in these files, never reset to a commit, so a moved upstream tag would silently change the Qt source built into the release. Pin the qt5 superproject to its v5.15.19-lts-lgpl commit and let it resolve the submodules (git submodule update on linux/windows, init-repository on android), so only the qt5 hash is hardcoded. qt5 records the exact submodule commits, and the relative .gitmodules URLs keep the fetches on https. Follow-up to #4613.
* | docker: update libgpg-error and libgcrypt reposelsta2026-06-261-2/+2
|/
* Dockerfiles: fetch dependencies over https instead of git:// / http://Thomas2026-06-221-14/+14
| | | | | | | | | The release Dockerfiles cloned Qt (code.qt.io) and libgpg-error/libgcrypt (git.gnupg.org) over unauthenticated git://, and fetched libiconv (ftp.gnu.org) over http://. Qt is tag-pinned only, so a MITM on its clone could substitute source into the build. Switch them all to https, like every other dependency in these files. The gnupg commit pins and the libiconv sha256sum are unchanged.
* docker: update Qt to 5.15.19selsta2026-05-191-1/+1
|
* build: prepare v0.18.5.0selsta2026-05-041-2/+2
|
* build: prepare v0.18.4.6selsta2026-02-231-2/+2
|
* docker: update Qt to 5.15.18selsta2026-01-311-1/+1
|
* build: prepare v0.18.4.5selsta2026-01-051-2/+2
|
* build: prepare v0.18.4.4selsta2025-11-121-2/+2
|
* Merge pull request #4507luigi11112025-10-071-2/+2
|\ | | | | | | c285879 build: prepare v0.18.4.3 (selsta)
| * build: prepare v0.18.4.3selsta2025-10-071-2/+2
| |
* | docker: update Qt to 5.15.17selsta2025-09-031-1/+1
|/
* build: prepare v0.18.4.2selsta2025-08-241-2/+2
|
* build: prepare v0.18.4.1selsta2025-07-171-2/+2
|
* build: prepare v0.18.4.0selsta2025-03-291-2/+2
|
* docker: update Qt to 5.15.16selsta2024-11-201-1/+1
|
* docker: bump Qt to v5.15.14tobtoht2024-05-241-1/+1
|
* docker: bump Qt to v5.15.13tobtoht2024-03-121-1/+1
|
* docker: update Qt to 5.15.12selsta2024-01-041-1/+1
|
* docker: update Linux & Windows Qt to 5.15.11tobtoht2023-10-041-1/+1
|
* docker: update Linux & Windows Qt to 5.15.10tobtoht2023-06-061-1/+1
|
* Merge pull request #4120luigi11112023-02-251-2/+2
|\ | | | | | | a50491d build: prepare v0.18.2.0 (selsta)
| * build: prepare v0.18.2.0selsta2023-02-181-2/+2
| |
* | docker: update Windows and Linux Qt to 5.15.8selsta2023-01-161-1/+1
|/
* docker: update Qt to 5.15.7selsta2022-11-131-1/+1
|
* docker: update qt to 5.15.6tobtoht2022-09-091-1/+1
|
* Dockerfile: fix hashselsta2022-08-101-1/+1
|
* build: prepare v0.18.1.0selsta2022-08-101-1/+1
|
* build: prepare v0.18.0.0selsta2022-07-151-2/+2
|
* docker: update Qt to 5.15.5selsta2022-06-211-1/+1
|
* docker: qt 5.15.4selsta2022-05-121-1/+1
|
* Docker: update Qt 5.15.2 -> 5.15.3selsta2022-03-251-1/+1
|
* build: prepare v0.17.3.0selsta2021-11-301-2/+2
|
* docker: Windows - use Qt 5.15.2xiphon2020-12-261-12/+23
|
* docker: Windows static build (cross-compilation from Linux)xiphon2020-09-201-0/+71