mirror of
https://github.com/RayLabsHQ/gitea-mirror.git
synced 2026-05-21 23:21:43 -05:00
[PR #295] [MERGED] chore: bump and digest-pin Bun base image to 1.3.14 #3019
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/RayLabsHQ/gitea-mirror/pull/295
Author: @arunavo4
Created: 5/19/2026
Status: ✅ Merged
Merged: 5/19/2026
Merged by: @arunavo4
Base:
main← Head:ci/pin-bun-docker📝 Commits (1)
03fcc57chore: bump and digest-pin Bun base image to 1.3.14📊 Changes
1 file changed (+2 additions, -2 deletions)
View changed files
📝
Dockerfile(+2 -2)📄 Description
Summary
Extends the supply-chain hardening from #293 (GitHub Actions → SHA pins) to the Dockerfile.
oven/bun:1.3.13-debian→1.3.14-debian(released 2026-05-13)@sha256:9dba1a1b43ce28c9d7931bfc4eb00feb63b0114720a0277a8f939ae4dfc9db6f(multi-arch manifest list, covers bothlinux/amd64andlinux/arm64)baseandrunnerstages so every layer derives from the exact same digestA tag like
1.3.14-debianis mutable on Docker Hub the same way a GH Action tag is mutable on GitHub — the maintainer can re-push it to a different image at any time. Pinning to the digest means even a compromised Docker Hub account can't change what we pull on the next build.Test plan
oven/bun:1.3.14-debianexists on Docker Hub and resolved its multi-arch digestdockerjob pulls the new digest and builds successfully (validates the digest is correct and the image is reachable from GitHub runners)Follow-ups not in this PR
BUN_VERSION: "1.3.13"ine2e-tests.ymland the bare1.3.13literal inastro-build-test.yml— those install Bun on the runner viaoven-sh/setup-bun, separate concern from the Docker base image. Worth bumping to match, but not strictly part of "pin the image."🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.