gate(owner): release sequant 3.0.0 — `/release` major from `main` after the smoke and the pin; `next` first, `latest` on the owner's word

Aperta
  • Qualcosa non va?
#1,657 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à
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
1/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
github, typescript
Ambito
release

Direzione di ricerca

Read the [Unreleased] section of CHANGELOG.md on main and review the smoke report in #1655; #1655 and #1656 must be complete first. The release runs through /release's PR #1131, with package.json, package-lock.json and CHANGELOG.md named as the files it may touch. The owner must decide separately whether to publish 3.0.0 to next and promote it to latest; done means the npm version and tag exist, the changelog lists the removals, and the baseline tag remains untouched.

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

Descrizione

graph-2026-11-simplify

Epic: graph-2026-11-simplify Tier: mechanical Execution: owner Blocked by: #1655, #1656

  • Blocked by: #1655
  • Blocked by: #1656

Problem

#1647 to #1649 remove flags, a setting and an MCP parameter, so the release is a semver major. The owner decided on 2026-11-03 that the simplification lands on main as 3.0, with no fork, and that 3.0 waits for the downstream pin. Founding doc P-13.

The gate

  • Artifact reviewed: the [Unreleased] section of CHANGELOG.md on main and the smoke report (#1655).
  • Question the owner answers: publish 3.0.0 to next? Then, separately: promote to latest?
  • Reject route: a changelog gap reopens the node that owns it; a smoke reopen already blocks this node.

Acceptance Criteria

  • AC-1: 3.0.0 is on npm. Evidence: npm view [email protected] version → 3.0.0
  • AC-2: The release tag exists. Evidence: git ls-remote --tags origin v3.0.0 | wc -l | tr -d ' ' → 1
  • AC-3: The 3.0.0 changelog section lists the removals. Evidence: awk '/^## \[3\.0\.0\]/,/^## \[2\./' CHANGELOG.md | grep -cE -- '--model-ladder|--escalate-effort|--stacked|--reflect|--full-qa' → ≥ 5
  • AC-4: The measured build's tag is untouched. Evidence: git rev-parse 'research-baseline-2026-11-03^{commit}' | cut -c1-9 → 31c6f8bdc (constraint)

May touch

package.json, package-lock.json, CHANGELOG.md through /release's PR (#1131).

Non-Goals

  • Promoting to latest without the owner's second answer.
  • Anything not merged by #1646 to #1652.

Done when

[email protected] is published with a changelog that names every removal, and the production executor still runs 2.20.0.

Lingua principale
TypeScript
Stelle
1
Fork
1
Merge medio
11h 3m
PR unite (30g)
84

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 sequant-io/sequant

Tutte le issue di sequant-io/sequant

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.