We build the orchestrator from this repo's source in our own environment, and we used to pin deployments to the weekly 2026.xx tags. Since the release flows moved into belt (commit af29d4e, 2026-08-05), this repo gets no git tags anymore.
Would it be possible for belt to also push a -v git tag every time it pushes a chore(main): release commit to this repo? No GitHub Release is needed — a plain tag would be enough.
This is the only thing I'd like to ask for. if it's not feasible, feel free to close this. Thanks!
We build the orchestrator from this repo's source in our own environment, and we used to pin deployments to the weekly 2026.xx tags. Since the release flows moved into belt (commit af29d4e, 2026-08-05), this repo gets no git tags anymore.
Would it be possible for belt to also push a -v git tag every time it pushes a chore(main): release commit to this repo? No GitHub Release is needed — a plain tag would be enough.
This is the only thing I'd like to ask for. if it's not feasible, feel free to close this. Thanks!