You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
build(release): v4 is a branch now, and the tag that pretended to be one is gone
A ref that moves should look like one. `v4` was a tag this repository
force-pushed onto every release, so `dAppCore/build@v4` meant different
code from one afternoon to the next while looking pinned — which is how
lthn/desktop asked for darwin:package, got it, and then got darwin:build
from the same unchanged line. It is a branch at the same name, so @v4
still resolves and now says what it does.
Version tags stay exactly as they are: cut once, never moved. Consumers
pin those. The manifests reach each other at @v4 so consuming the branch
runs the whole tree rather than a new root over frozen sub-actions, and
that is what our own repositories use — better it breaks for us.
v4-branch.yml fast-forwards the branch from main, and refuses if the two
have diverged rather than discarding anything. scripts/release.sh cuts a
tag on a detached commit with the internal references rewritten to that
version, leaving the branch alone.
Co-Authored-By: Virgil <virgil@lethean.io>
0 commit comments