ci(til): cite the paper that describes this release, not the first arxiv tag - #86
Merged
Merged
Conversation
…xiv tag Second recurrence of one pattern: lifting an identifier off a model card without checking which artifact it refers to. - PR #77 listed arXiv 2310.10688 under "TimesFM 3.0 specifications". That is Das et al. 2023, the original TimesFM paper, cited on the card only for project lineage. - PR #85 cites arXiv 2506.07900 as MiniCPM5-2B's technical report. The card carries two arxiv tags, 2506.07900 and 2602.09003; the agent took the older. Same shape as the pricing bug fixed in #80, which is why the rule sits next to it: read every arxiv tag, prefer the newest unless the card ties an older ID to this version, and say the report was not identified rather than guess. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Vru5xPN55JPU7dyVS3uswd
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe workflow now instructs the agent to identify the technical report for the reviewed release. The generated lock metadata hash was updated to match the workflow content. ChangesCitation guidance
Estimated code review effort: 1 (Trivial) | ~2 minutes Severity of issue fixed: Low ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
4 tasks
sameerkhansf
added a commit
that referenced
this pull request
Sep 8, 2026
…sed one (#87) Three live posts corrected, and the guardrail I added in #86 replaced because it would not have caught the case that prompted it. 1. minicpm5-2b-review-2026: cited arXiv:2506.07900 as MiniCPM5-2B's technical report. That paper is "MiniCPM4: Ultra-Efficient LLMs on End Devices" (June 2025) — the previous generation. The card's other tag, 2602.09003, is "Data Science and Technology Towards AGI Part I: Tiered Data Management". Neither describes MiniCPM5, so the post now says so instead of promoting a near-miss. Both titles read off arxiv.org/abs/<id>. 2. glm-5-3-review-2026 and glm-5-3-flash-vs-qwen3-8-flash-next-comparison-2026: both listed the context length as 300K. That number is the evaluation context for the HLE benchmark in the cards' footnotes; config.json gives max_position_embeddings = 1048576 for both models. Same failure as the pricing bug — a footnote figure promoted to a spec. 3. The #86 rule said "prefer the newest arxiv tag unless the card ties an older one to this version". Applied to MiniCPM5-2B that picks 2602.09003, which is also wrong. Any ordering heuristic fails here, because the tag list carries no guarantee at all. Replaced with: fetch arxiv.org/abs/<id>, read the title, and cite it only if the title names this model and version. Claude-Session: https://claude.ai/code/session_01Vru5xPN55JPU7dyVS3uswd Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Caught while reviewing #85, the first post the pipeline has produced since it was unblocked.
Second recurrence of one pattern — lifting an identifier off a model card without checking which artifact it refers to:
arxiv:2506.07900andarxiv:2602.09003— it took the olderSame shape as the pricing bug fixed in #80, so the rule sits directly next to it: read every
arxiv:tag, prefer the newest unless the card explicitly ties an older ID to this version, and say the technical report was not identified rather than guess.Verified against the source
Everything else in #85 checks out — Apache-2.0, en/zh, text-generation, genuinely 2 days old.
Verification
gh aw compile— 4 workflows succeedednpm run lintclean🤖 Generated with Claude Code
https://claude.ai/code/session_01Vru5xPN55JPU7dyVS3uswd
Summary by CodeRabbit