Skip to content

Open-source speech recognition toolkit for training, inference, streaming ASR, VAD, punctuation, speaker diarization pipelines, and OpenAI-compatible/MCP serving.

Refresh discussion pin API evidence (#3386)

zhifu gaoddd0e74ccde4
diff --git a/docs/community_growth_20k.md b/docs/community_growth_20k.md
index fc2de5eae..9b6117388 100644
--- a/docs/community_growth_20k.md
+++ b/docs/community_growth_20k.md
@@ -367,7 +367,7 @@ Paste the Markdown output into launch notes, weekly community updates, or releas
### Week 4: Distribution and feedback
- [x] Share the release in relevant developer communities. On 2026-07-23, GitHub Discussion [`modelscope/FunASR#3376`](https://github.com/modelscope/FunASR/discussions/3376) was published in the `Announcements` category with the title `FunASR v1.3.26: OpenAI-compatible ASR deployment, vLLM, and llama.cpp runtime`. It routes readers to `funasr==1.3.26`, `/v1/audio/transcriptions`, WebSocket realtime examples, `docs/vllm_guide.md`, the H100 vLLM smoke evidence, `runtime-llamacpp-v0.1.8`, troubleshooting docs, and asks real app users to share hardware, model path, latency, and deployment friction.
-- [ ] Pin a GitHub discussion for the release. The release discussion exists at [`modelscope/FunASR#3376`](https://github.com/modelscope/FunASR/discussions/3376), but the GitHub GraphQL API currently exposes `createDiscussion` and `updateDiscussion` but no discussion pin mutation; pin manually in the GitHub Discussions UI or retry if GitHub exposes an API for discussion pinning.
+- [ ] Pin a GitHub discussion for the release. The release discussion exists at [`modelscope/FunASR#3376`](https://github.com/modelscope/FunASR/discussions/3376) with GraphQL node `D_kwDOIfjis84An-Vp` in the `Announcements` category. A 2026-07-23 GraphQL schema recheck found discussion mutations `createDiscussion`, `updateDiscussion`, `closeDiscussion`, `reopenDiscussion`, `deleteDiscussion`, and discussion-comment mutations, but still no `pinDiscussion` / `unpinDiscussion`; only `pinIssue`, `pinIssueComment`, and `pinEnvironment` are exposed. Pin manually in the GitHub Discussions UI or retry if GitHub adds a discussion pin mutation.
- [x] Triage all new issues within 48 hours. On 2026-07-23, all four repositories were patrolled with the GitHub token on `ind-gpu8`: `modelscope/FunASR`, `FunAudioLLM/Fun-ASR`, `FunAudioLLM/SenseVoice`, and `modelscope/FunClip` all had `0` open pull requests; Fun-ASR, SenseVoice, and FunClip had `0` open issues. The only open FunASR issues were already triaged: #3302 is labeled `question` + `needs feedback` and is waiting for the reporter to retest the merged hotword/postprocess fix, while #3104 is labeled `enhancement` + `needs maintainer decision` and is waiting on release-scope confirmation for RL training code. No unlabelled or unowned open issue remained in the 48-hour window.
- [x] Convert top 3 support questions into docs. On 2026-07-23, the latest 80 FunASR issues were triaged into three repeat support blockers: install / hub / model-id selection (#3321, #3045, #3042, #2973, #2976), llama.cpp / GGUF / CUDA-Vulkan runtime packages (#3298, #3297, #3296, #3289, #3243), and realtime / VAD / vLLM / server output behavior (#3101, #3109, #3038, #3031, #2968, #2965). `docs/troubleshooting.md` and `docs/troubleshooting_zh.md` now start with a Top support questions section that maps those three issue clusters to the existing install, model-download, OpenAI-compatible server, WebSocket, and llama.cpp / GGUF FAQ anchors.
- [ ] Track stars, PyPI downloads, issue volume, and docs traffic. `collect_growth_metrics.py` now tracks GitHub stars, open issues, and open pull requests for the four core repositories and adds PyPIStats download windows for `funasr` as `downloads_last_7_days` and `downloads_last_30_days` when `pypistats.org` is reachable. The script keeps the patrol usable when PyPIStats is rate-limited by reporting downloads as unavailable instead of failing the run. GitHub/PyPI tracking is now covered; docs traffic remains unavailable until an analytics credential or export is connected.
diff --git a/tests/test_growth_plan_doc.py b/tests/test_growth_plan_doc.py
index 30f0ed928..594401c94 100644
--- a/tests/test_growth_plan_doc.py
+++ b/tests/test_growth_plan_doc.py
@@ -208,6 +208,27 @@ def test_growth_plan_records_sharp_github_release_focus():
assert "[ ] Create a GitHub release focused on one sharp value proposition" not in text
+def test_growth_plan_records_discussion_pin_api_blocker():
+ text = PLAN.read_text()
+
+ required_markers = [
+ "[ ] Pin a GitHub discussion for the release",
+ "`modelscope/FunASR#3376`",
+ "`D_kwDOIfjis84An-Vp`",
+ "`Announcements` category",
+ "`createDiscussion`",
+ "`updateDiscussion`",
+ "`closeDiscussion`",
+ "`reopenDiscussion`",
+ "no `pinDiscussion` / `unpinDiscussion`",
+ "`pinIssue`",
+ "`pinIssueComment`",
+ "`pinEnvironment`",
+ ]
+ for marker in required_markers:
+ assert marker in text
+
+
def test_growth_plan_records_issue_triage_completion():
text = PLAN.read_text()
@@ -316,7 +337,8 @@ def test_growth_plan_records_release_discussion_distribution():
"Announcements",
"`/v1/audio/transcriptions`",
"`runtime-llamacpp-v0.1.8`",
- "GitHub GraphQL API currently exposes `createDiscussion` and `updateDiscussion` but no discussion pin mutation",
+ "no `pinDiscussion` / `unpinDiscussion`",
+ "`pinIssue`, `pinIssueComment`, and `pinEnvironment`",
"[ ] Pin a GitHub discussion for the release",
]
for marker in required_markers: