Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Stop building and pushing container images outside a release

オープン
  • 何か問題がありますか？
#881 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
30/100
issue の種類
リファクタリング
明瞭さ
おおむね明確
活発さ
活発
技術スタック
docker, github-actions
領域
devops, documentation, infrastructure, release

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.
主要言語
TypeScript
スター
829
フォーク
234
平均マージ
18時間 43分
マージ済み PR（30日）
67

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

cameri/nostream のほかの issue

cameri/nostream の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。