v2.102.3

• Keep RELEASE_PATHS in mise.toml and ask mise run release-due, as every one of danielbodart's repos does, from CI and from the weekly update, which now dispatches a release with exactly if mise run release-due; then gh workflow run ci.yml ... -f release=true; fi; run every step under bash, so -eo pipefail stops a failed flake update or digest lookup on the left of a pipe from going ahead with what it printed (and a lookup that names no digest fails the week rather than writing one into the Dockerfile); name the tarballs as every tool's are, -linux-x86_64, -aarch64 and -armv7.tar.gz, the plain binaries keeping the names links point at; write each release's notes from the commits since the last one; and say how it ships under Channels in the shape every README uses (73b7998)

Image: danielbodart/portical:2.102.3 or ghcr.io/danielbodart/portical:2.102.3