Release: dev → main (first public release) #258

Merged
bvandeusen merged 94 commits from dev into main 2026-09-25 10:02:40 -04:00
Showing only changes of commit f0595e43e6 - Show all commits
+13 -6
View File
@@ -1718,12 +1718,19 @@ jobs:
# ONLY, so an index sitting at :refresh-candidate would fail its # ONLY, so an index sitting at :refresh-candidate would fail its
# `test -n "$CT"` and break the weekly refresh for this name. # `test -n "$CT"` and break the weekly refresh for this name.
# #
# The layers were just built on this runner pool, so the pull is # MEASURED on run 7300, the first execution: the push moved ZERO
# normally local. The push sends only blobs the destination lacks — # layer bytes. Every blob came back either "Layer already exists" or
# whether the registry shares them across two repositories of one # "Mounted from bvandeusen/fabledcurator" — the registry does
# owner is not something this file should assume, and the first run's # cross-repository blob mounts between two repos of one owner, so
# output answers it. Either way it moves no more bytes than the # this copies a manifest and nothing else. 22s, against the ~2min
# duplicate build's own push did, and it compiles nothing. # the duplicate build cost (run 7282: build-ml 1m55s).
#
# The pushed manifest gets its OWN digest (b979b145… where the
# source was aca4c75…) because docker re-serialises it. Same layers,
# same config, same fc.revision; only the manifest bytes differ.
# Nothing compares the two, and promote reads whatever is at the tag
# — but it is worth saying, because the digests looking different is
# the first thing someone will notice and misread as a second build.
docker pull "$SRC@$DIGEST" docker pull "$SRC@$DIGEST"
for t in $TAGS; do for t in $TAGS; do
echo "alias: $DST:$t -> $SRC@$DIGEST" echo "alias: $DST:$t -> $SRC@$DIGEST"