brev/launch-nemoclaw.sh: pin PLUGIN_REF and COMMUNITY_REF to stable tags instead of main

Aperta
#64 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
git, shell
Ambito
devops, release

Direzione di ricerca

Start with brev/launch-nemoclaw.sh and verify the available tags and branch backing the public launchable, noting that OpenShell-Community currently has no tag to use. Coordinate creation of a stable community tag, then update the script defaults to the matching community and NemoClaw tags; this is done when deployments no longer default to main and future release-time bumps are defined.

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

Descrizione

Problem

brev/launch-nemoclaw.sh on feat/brev-nemoclaw-plugin defaults both refs to main:

# line 22
COMMUNITY_REF="${COMMUNITY_REF:-${COMMUNITY_BRANCH:-main}}"
# line 26
PLUGIN_REF="${PLUGIN_REF:-main}"

The public NVIDIA Brev launchable (build.nvidia.com/nemoclaw → Try Early Preview) runs this script on every deploy. Tracking main means each user gets whatever HEAD is at that moment — behavior drifts, regressions ship silently to end users, and reproducing a bug report is impossible without a commit SHA.

Reported upstream in NVIDIA/NemoClaw#1242 by NV QA.

Constraint

  • NVIDIA/NemoClaw has git tags (latest v0.0.18) — PLUGIN_REF can pin to one today.
  • NVIDIA/OpenShell-Community has no tags and no releases — COMMUNITY_REF has nothing to pin to yet. Cutting a stable tag here is a prerequisite.

Proposed fix

  1. Cut a stable tag on feat/brev-nemoclaw-plugin (or the branch backing the public launchable) — e.g. brev-launchable-v0.0.18 matching NemoClaw's release.
  2. Update defaults in brev/launch-nemoclaw.sh: 
    COMMUNITY_REF="${COMMUNITY_REF:-brev-launchable-v0.0.18}"
PLUGIN_REF="${PLUGIN_REF:-v0.0.18}"
  3. Release-time bump — tie PLUGIN_REF updates to NemoClaw release cadence so the launchable always points at the latest stable pair.

Environment

Lingua principale
Dockerfile
Stelle
191
Fork
76
Nessuna PR unita negli ultimi 30g

Guida per i contributori

Apri la guida per i contributori

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 NVIDIA/OpenShell-Community

Tutte le issue di NVIDIA/OpenShell-Community

Issue simili

Altre issue su DevOps

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.