Restore <pkg>-v<ver> git tags for per-component releases

Open
#3,620 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
50/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
git
Domain
release

Research direction

Start by inspecting belt's release flow associated with commit af29d4eb and how it pushes the chore(main): release commits to this repository. Done means each such release also pushes a plain -v git tag, without creating a GitHub Release.

Written by the indexing model from the issue text.

Description

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 af29d4eb, 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!

Dominant language
Go
Stars
1.6k
Forks
438
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from e2b-dev/runtime

All issues in e2b-dev/runtime

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.