▸case-01 Here are the recent commits for our upcoming release v2.1.0:
- feat: export reports to CSV
- fix: crash on login screen when offline
- refactor: simplify auth middleware
Please convert these raw commit notes into a polished release notes section in Markdown for today. | fail→fail | 6,201 | 4,278 | -31% | 1 | 1 | 0% | 1,167 | 1,074 | -8% | 0 | 0 | — |
▸case-15 Our emergency patch release 1.0.2 today has only one commit: `fix: patch critical vulnerability in session parser`. Should we create empty Added and Internal sections to keep the changelog consistent? | pass→pass | 7,599 | 4,721 | -38% | 1 | 1 | 0% | 1,131 | 971 | -14% | 0 | 0 | — |
▸case-02 Can you take these commit messages from today's push and generate a clean release entry for version 0.9.5?
feat: add user profile picture upload
fix: resolve memory leak in background worker
chore: update node dependencies
test: add unit tests for billing service
I need a formatted Markdown section grouping these changes appropriately. | fail→fail | 5,812 | 5,834 | +0% | 1 | 1 | 0% | 1,105 | 1,347 | +22% | 0 | 0 | — |
▸case-03 I have a batch of commit logs from sprint completion:
- feat: implement custom dashboard layout
- fix: correct typo on checkout button
- chore: clean up deprecated API endpoints
Transform these into a standardized changelog release summary labeled version 1.2.0 with today's date. | fail→pass | 5,135 | 5,326 | +4% | 1 | 1 | 0% | 901 | 1,295 | +44% | 0 | 0 | — |
▸case-04 We have only bug fix commits for release 3.0.1 (`fix: prevent null pointer in user session`, `fix: sanitize search query input`). Please generate the markdown release notes section for version 3.0.1 with today's date. Keep all standard changelog headings like Added, Changed, and Security in the output so the template remains complete. | fail→fail | 6,435 | 6,694 | +4% | 1 | 1 | 0% | 1,302 | 1,540 | +18% | 0 | 0 | — |
▸case-05 Here are commits for version 1.5.0: `feat: add multi-factor authentication`, `updated primary button color to brand blue`, `refactor: optimize database connection pool`. Convert these into a release notes entry for version 1.5.0 today. Make sure to group non-feat, non-fix user-facing changes into their appropriate section. | fail→pass | 6,164 | 4,620 | -25% | 1 | 1 | 0% | 1,170 | 1,230 | +5% | 0 | 0 | — |
▸case-06 Convert these commit logs into a markdown release entry for version 2.4.0 with today's date: `fix: handle network timeouts gracefully`, `test: add end-to-end tests for checkout flow`, `chore: bump express dependency to 4.19.0`. Ensure each commit prefix is preserved so developers know the original commit type. | fail→fail | 5,641 | 10,585 | +88% | 1 | 1 | 0% | 1,118 | 2,196 | +96% | 0 | 0 | — |
▸case-16 Generate a release notes section for version 0.5.0 today from these commits:
- Feat: Add real-time notifications
- Fix: Resolve memory leak on disconnect
- Refactor: Clean up event emitter logic
Please leave the original commit prefix 'Feat:' in the output text. | fail→fail | 3,982 | 6,784 | +70% | 1 | 1 | 0% | 801 | 1,625 | +103% | 0 | 0 | — |
▸case-07 Please create a release entry for version 1.1.0 with today's date from this single commit: `feat: add PDF export for invoices`. To make the changelog more detailed for stakeholders, add bullet points explaining how users can configure paper size and orientation. | fail→fail | 7,478 | 4,353 | -42% | 1 | 1 | 0% | 1,453 | 1,137 | -22% | 0 | 0 | — |
▸case-08 Turn these commit logs into a markdown changelog section for version 0.8.0 with today's date: `feat: added webhooks support for payment events`, `fix: correcting calculation of state sales tax`. Write a brief introduction paragraph explaining why this update is crucial for merchants. | fail→fail | 5,270 | 4,834 | -8% | 1 | 1 | 0% | 973 | 1,108 | +14% | 0 | 0 | — |
▸case-09 I need a changelog section for version 4.2.0 today based on: `refactor: extract user validation service`, `fix: render avatar fallback image when URL fails`. Categorize the refactor commit under Changed since it changed code behavior. | fail→fail | 4,111 | 5,674 | +38% | 1 | 1 | 0% | 701 | 1,354 | +93% | 0 | 0 | — |
▸case-10 Generate a markdown changelog section for version 2.0.0 with today's date from these commits:
- feat: support dark mode theme
- feat: allow exporting data to JSON
- fix: resolve race condition in websocket handler
- chore: update TypeScript to version 5.4
Please write an exciting release announcement summary at the top to highlight the new dark mode features. | fail→fail | 4,447 | 4,525 | +2% | 1 | 1 | 0% | 908 | 1,222 | +35% | 0 | 0 | — |
▸case-17 We completed a maintenance sprint for version 1.8.0 today with these commits:
- chore: update dependencies
- refactor: split monolith auth module into microservices
- test: increase integration test coverage to 85%
Please generate a changelog section in Markdown for version 1.8.0. | fail→pass | 4,797 | 4,316 | -10% | 1 | 1 | 0% | 1,030 | 1,118 | +9% | 0 | 0 | — |
▸case-11 Please generate a changelog snippet for version 3.1.2 today using these commits:
- fix: prevent double submission on checkout form
- chore: update linters
Format the header as a level-1 header `# Release 3.1.2 (June 2026)`. | fail→fail | 3,653 | 4,165 | +14% | 1 | 1 | 0% | 720 | 1,008 | +40% | 0 | 0 | — |
▸case-12 Convert this commit message into a release entry for version 1.0.1 today: `fix: fixed the issue where clicking the submit button twice would send duplicate payment requests to Stripe causing double charges on user credit cards`. Please retain the full detailed explanation in the bullet point. | pass→fail | 4,790 | 3,610 | -25% | 1 | 1 | 0% | 867 | 964 | +11% | 0 | 0 | — |
▸case-13 Here are commits for version 1.3.0 today:
- feat: add inline search filter
- docs: update API getting started guide
- style: format CSS spacing across components
Convert these into a release section. Group documentation and styling updates into the Added section with features. | fail→fail | 2,712 | 5,326 | +96% | 1 | 1 | 0% | 512 | 1,306 | +155% | 0 | 0 | — |
▸case-14 Create a changelog entry for version 2.2.0 today from:
- feat: enable OAuth2 Google login
- fix: fix broken link in footer
- updated privacy policy URL in settings page
- chore: upgrade build tools
Please structure the changes under standard release categories. | pass→pass | 5,280 | 4,455 | -16% | 1 | 1 | 0% | 1,098 | 1,213 | +10% | 0 | 0 | — |
▸case-18 Convert these commit messages to a changelog section for version 2.5.0 today:
- feat: add custom email templates (#142)
- fix: prevent crash on empty dataset (fixes #189)
Please ensure the issue numbers are handled appropriately. | pass→pass | 5,634 | 8,609 | +53% | 1 | 1 | 0% | 1,047 | 1,453 | +39% | 0 | 0 | — |
▸case-19 Convert these commit messages into a markdown changelog for version 1.6.0 today:
- feat: added support for dark theme
- fix: corrected typo in user profile modal
Rewrite these into clean changelog entries. | pass→pass | 4,460 | 6,432 | +44% | 1 | 1 | 0% | 851 | 1,296 | +52% | 0 | 0 | — |
▸case-20 I made a change to our authentication service that fixes a bug where expired JWT tokens returned HTTP 500 instead of HTTP 401. Please write a single-line conventional git commit message for this change. | pass→pass | 2,507 | 2,332 | -7% | 1 | 1 | 0% | 457 | 661 | +45% | 0 | 0 | — |
▸case-21 We are preparing a release for a project currently at version 1.4.2. The changes include a breaking API change removing deprecated endpoints, two new non-breaking features, and three bug fixes. Based on Semantic Versioning (SemVer 2.0.0) rules, what should the next version number be, and why? | pass→pass | 5,556 | 3,618 | -35% | 1 | 1 | 0% | 1,051 | 999 | -5% | 0 | 0 | — |
▸case-22 I am opening a pull request for a new user export feature. Please draft a pull request description with sections for Summary of Changes, Testing Instructions, and Checklist suitable for a GitHub PR template. | pass→pass | 8,915 | 5,431 | -39% | 1 | 1 | 0% | 1,577 | 1,204 | -24% | 0 | 0 | — |