loot / libloot

93%

master: 94%

LAST BUILD ON BRANCH remove-32-bit-builds

branch: remove-32-bit-builds

CHANGE BRANCH

x

Reset

Sync Branches

• remove-32-bit-builds
• actions-permissions
• add-audits
• better-error-line-numbers
• c++20
• c++20-wrapper
• c4711
• cargo-vet
• ci-npm-cache
• ci-updates
• cmake-vars
• coverage-ci
• cxx-fix
• decouple-condition-cache
• dependency-notices
• disable-cxx-lto
• emit-anchors-aliases
• fix-dependabot
• fix-metadata-write
• fix-msvc-warning
• fix-node-vulns
• fix-permission
• improve-readmes
• master
• misc
• misc-changes
• misc-fixes
• prep-0.28.2
• prevent-base-class-slicing
• regex-fix
• regress
• release-0.28.4
• rename-target
• replace-install-action
• rust-rewrite
• support-symlinks
• symlink-support
• test-long-paths
• undo-cargo-toml-change
• unique-plugin-interface
• update-audits
• update-c++-game-wrapper
• update-cxx
• update-deps
• update-doc
• update-docs
• update-lci
• update-locks
• update-napi-build
• update-napi-rs
• update-nodejs-lockfiles
• update-regress
• update-release-job
• update-rust-ini
• userlist-parity
• uv-ci
• yaml-fixes

Build # 20642149423

Build Type

push

github

Committed by Ortham

Commit Message

Stop running 32-bit CI and release builds

This only affects Windows builds, as Linux builds are already
64-bit-only. I'm not aware of any current dependents of the 32-bit
release binaries.

32-bit Windows is well on its way to being unsupported: Windows 11 is
64-bit only, and Windows 10 Home and Pro only receive security updates
if you've opted into extended security updates (which I have). Steam's
survey puts Windows 10 32-bit usage at less than 0.05% of installs, and
Steam itself dropped support for 32-bit Windows today.

Given that, I don't think it's worth running 32-bit builds or producing
32-bit release binaries. I won't intentionally break libloot working on
32-bit Windows, but it might now happen without me noticing.

Run Details

11162 of 11961 relevant lines covered (93.32%)

142.04 hits per line