Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Stop building and pushing container images outside a release

Aperta
  • Qualcosa non va?
#881 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
30/100
Tipo di issue
Refactoring
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
docker, github-actions
Ambito
devops, documentation, infrastructure, release

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.
Lingua principale
TypeScript
Stelle
829
Fork
234
Merge medio
18h 43m
PR unite (30g)
67

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di cameri/nostream

Tutte le issue di cameri/nostream

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.