Skip to content

📝 docs(skills): record contributor roster in version-release#14219

Merged
arvinxx merged 1 commit into
canaryfrom
docs/release-skill-contributors
Apr 27, 2026
Merged

📝 docs(skills): record contributor roster in version-release#14219
arvinxx merged 1 commit into
canaryfrom
docs/release-skill-contributors

Conversation

@arvinxx

@arvinxx arvinxx commented Apr 27, 2026

Copy link
Copy Markdown
Member

Summary

Captures the contributor-section conventions surfaced during the v2.1.53 weekly release writeup so future runs of /version-release produce the same output without back-and-forth.

  • Add a Contributor Ordering section with the canonical LobeHub team roster (10 handles) and a flat-list rule (community first, team after, sorted by PR count desc).
  • Note the git-author-name vs GitHub-handle pitfall (e.g. YuTengjing@tjx666) and how to resolve it via gh pr view <PR> --json author / gh api search/users.
  • Update the changelog template: drop commits count from both the metadata and contributors lines; reword the contributors intro to a Huge thanks to N contributors who shipped N merged PRs pattern.

Test plan

  • Skill markdown renders cleanly (Markdown lint via prettier hook passes)
  • Next weekly release uses the new conventions without manual nudging

- Add Contributor Ordering section with the canonical LobeHub team roster (10 handles) and a flat-list rule (community first, team after, sorted by PR count desc).
- Note the git-author-name vs GitHub-handle pitfall (e.g. YuTengjing -> @tjx666) and how to verify via gh CLI.
- Drop commits count from the changelog template's metadata and contributors lines; reword the contributors intro to a "Huge thanks to N contributors" pattern.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@vercel

vercel Bot commented Apr 27, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
lobehub Ready Ready Preview, Comment Apr 27, 2026 5:06am

Request Review

@dosubot dosubot Bot added the size:M This PR changes 30-99 lines, ignoring generated files. label Apr 27, 2026

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We've reviewed this pull request using the Sourcery rules engine

@codecov

codecov Bot commented Apr 27, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 68.06%. Comparing base (3e236ec) to head (93868cd).
⚠️ Report is 4 commits behind head on canary.

Additional details and impacted files
@@            Coverage Diff             @@
##           canary   #14219      +/-   ##
==========================================
- Coverage   68.07%   68.06%   -0.01%     
==========================================
  Files        2261     2261              
  Lines      194144   194144              
  Branches    19531    20312     +781     
==========================================
- Hits       132154   132152       -2     
- Misses      61861    61863       +2     
  Partials      129      129              
Flag Coverage Δ
app 61.55% <ø> (-0.01%) ⬇️
database 92.04% <ø> (ø)
packages/agent-runtime 79.93% <ø> (ø)
packages/context-engine 83.25% <ø> (ø)
packages/conversation-flow 92.40% <ø> (ø)
packages/file-loaders 87.02% <ø> (ø)
packages/memory-user-memory 74.74% <ø> (ø)
packages/model-bank 99.89% <ø> (ø)
packages/model-runtime 84.28% <ø> (ø)
packages/prompts 68.17% <ø> (ø)
packages/python-interpreter 92.90% <ø> (ø)
packages/ssrf-safe-fetch 0.00% <ø> (ø)
packages/utils 88.41% <ø> (ø)
packages/web-crawler 88.66% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Components Coverage Δ
Store 67.20% <ø> (ø)
Services 53.36% <ø> (ø)
Server 68.44% <ø> (-0.01%) ⬇️
Libs 53.30% <ø> (ø)
Utils 80.04% <ø> (ø)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@arvinxx arvinxx merged commit f32fff1 into canary Apr 27, 2026
39 of 40 checks passed
@arvinxx arvinxx deleted the docs/release-skill-contributors branch April 27, 2026 05:23
mutoe pushed a commit to mutoe/lobehub that referenced this pull request May 1, 2026
…#14219)

📝 docs(skills): record contributor roster in version-release skill

- Add Contributor Ordering section with the canonical LobeHub team roster (10 handles) and a flat-list rule (community first, team after, sorted by PR count desc).
- Note the git-author-name vs GitHub-handle pitfall (e.g. YuTengjing -> @tjx666) and how to verify via gh CLI.
- Drop commits count from the changelog template's metadata and contributors lines; reword the contributors intro to a "Huge thanks to N contributors" pattern.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:M This PR changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant