Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Stop building and pushing container images outside a release

Aberta
  • Algo errado?
#881 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
30/100
Tipo de issue
Refatoração
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
docker, github-actions
Domínio
devops, documentation, infrastructure, release

Direção de pesquisa

First resolve what image tag or digest relay.tnsor.network should deploy; the issue identifies this as a prerequisite. Read .github/workflows/checks.yml, .github/workflows/release.yml, and containers/nostream-dev-webhook/README.md, plus the relay deploy runbook. Done when main pushes publish no image, releases remain the only publisher, and the relay and deploy documentation no longer depend on unreleased :main.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

What happens

CI Checks (checks.yml) has a publish-container-image job that pushes ghcr.io/cameri/nostream on every push to main:

# .github/workflows/checks.yml:276
  publish-container-image:
    name: Build and push container image
    if: >-
      always() && github.event_name == 'push' && github.ref == 'refs/heads/main' &&
      …
      tags: |
        type=raw,value=main
        type=sha,prefix=sha-

Release (release.yml) pushes the same package on release: [published], which is the one time a published image should exist.

That was deliberate when it landed (#747, 14cca60, 2026-08-30): relay.tnsor.network deploys by pulling ghcr.io/cameri/nostream:main and recreating, so a merge needed a fresh image to deploy. The consequence is that the main tag is a moving pointer to unreleased main rather than a released artifact, and one docker pull ghcr.io/cameri/nostream can hand any consumer code that no release covers.

Requested change

Stop building and pushing outside a release. release.yml stays as the only publisher, and checks.yml builds without pushing (or stops building at all) if a PR-time image is worth keeping for smoke tests.

What has to move first

relay.tnsor.network pulls :main as its deploy mechanism — the server compose references POST /images/create?fromImage=ghcr.io/cameri/nostream&tag=main (containers/nostream-dev-webhook/.scratch/README.md) and the version-check row reads that digest. Removing the push without moving that consumer leaves the box unable to deploy; switching it needs a decision on what it tracks instead (latest release tag, a rolling edge tag built elsewhere, or a digest pinned per release).

Acceptance criteria

  • A push to main that publishes no release produces no new image in ghcr.io/cameri/nostream.
  • Publishing a release still produces a tagged image, and release.yml is the only job with packages: write.
  • Wherever :main is documented as a deploy target (containers/nostream-dev-webhook/README.md, the relay deploy runbook), the docs name the released tag instead.
  • relay.tnsor.network has a deploy path that does not depend on an image built from unreleased main.

Evidence

  • Run referenced in the request: actions/runs/39084587426, job 117548418140 — CI Checks, push to main, cancelled at 00:55:54Z while the publish job's prerequisites were still running.
  • .github/workflows/checks.yml:276-334 — the push, packages: write, and the type=raw,value=main tag.
  • .github/workflows/release.yml:3-5 — on: release: types: [published], the intended trigger.
Linguagem predominante
TypeScript
Estrelas
829
Forks
234
Merge médio
18h 43min
PRs com merge (30d)
67

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de cameri/nostream

Todas as issues de cameri/nostream

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.