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
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 1/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github, typescript
- Domain
- release
Research direction
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.
Written by the indexing model from the issue text.
Description
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 ofCHANGELOG.mdonmainand the smoke report (#1655). - Question the owner answers: publish 3.0.0 to
next? Then, separately: promote tolatest? - Reject route: a changelog gap reopens the node that owns it; a smoke
reopenalready 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
latestwithout 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.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 1
- Avg merge
- 11h 3m
- Merged PRs (30d)
- 84
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from sequant-io/sequant
-
graph-2026-11-simplify
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
sequant-io/sequant#1650 ·
Maintainers usually reply within 1 day
-
run: --phases does not suppress the UI-label test phase (determinePhasesForIssue adds it to an explicit list)Possibly taken @admarble claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
sequant-io/sequant#1631 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
sequant-io/sequant#1601 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sequant-io/sequant#1582 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 76/100
sequant-io/sequant#1381 ·
Maintainers usually reply within 1 day
All issues in sequant-io/sequant
Similar issues
-
content triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
tensorflow/tfjs#8754 ·
-
tool-submission
Difficulty 1/5 Under an hour Newbie friendliness 83/100
BraveOPotato/NoSignups#2348 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
code-yeongyu/oh-my-openagent#12784 ·
Maintainers usually reply within 1 day
-
external-issue to-triage
Difficulty 2/5 1-3 hours Newbie friendliness 71/100
Maintainers usually reply within 1 day