| [build] Keep Chrome dev/beta images on linux/amd64 only, resolve the latest rclone tag (#3188) * [ci] Keep Chrome dev/beta images on linux/amd64 only Chrome dev (153) and beta (152) are ahead of the Chromium driver packages, which follow the stable channel and currently top out at 151, so no matching driver major exists for those channels on arm64 and the build fails at install-chromedriver.sh. Stable Chrome images stay multi-arch, Firefox dev/beta are unaffected. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * [build] Resolve the latest rclone tag when building the video image RCLONE_VER pointed at v1.75-stable, a maintenance branch rclone has not cut yet, so `git clone -b` failed and the video image could not build. Default RCLONE_VER to "latest" and resolve it from the repository tags, following the same pattern as GO_VERSION. Only vX.Y.Z tags are considered so release candidates and one-off tags are ignored, and an explicit RCLONE_VER is still used as is. Verified in a container: the latest tag resolves to v1.75.0, the shallow clone succeeds and `make` builds rclone v1.75.0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * [build] Resolve the latest rclone tag by tag date GitHub releases are sorted by publish date, so the API gives the most recently tagged release, e.g. a v1.74.5 point release published after v1.75.0 wins over a plain version sort. `git ls-remote --sort=-creatordate` can not do this, sorting remote refs by date needs object data that is not available without a repository, so the version sorted tag list stays as a fallback when the API returns nothing, for instance when it is rate limited. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com> | 1 个月前 |