-
-
Notifications
You must be signed in to change notification settings - Fork 6
chore(release): v0.4.0 #262
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -8,6 +8,26 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 | |
|
|
||
|
|
||
|
|
||
|
|
||
| ## [0.4.0] - 2026-03-05 | ||
|
|
||
| ### Added | ||
| - visual validation, notable components, and Figma context improvements (#254) | ||
| - enhance Figma integration with full API property coverage (#251) | ||
| - Figma-specific agent prompts, auto-inject tokens, spec cap (#248) | ||
| - expose --max-cost CLI flag with cost threshold warnings (#247) | ||
| - unified task management across GitHub & Linear (#196) | ||
|
|
||
| ### Fixed | ||
| - show model name and cost in loop header (#249) | ||
| - add Tailwind v4 @theme inline guidance to prevent v3 patterns (#246) | ||
| - auto mode gets stuck in validation loop on pre-existing test failures (#245) | ||
| - prevent PR targeting same branch and duplicated prefix (#244) | ||
| - show task title instead of agent name in loop header (#242) | ||
|
|
||
| ### Changed | ||
| - add context-builder and task-executor tests (#250) | ||
|
|
||
| ## [0.3.1] - 2026-02-19 | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Missing CHANGELOG entry for v0.3.2 The Prompt To Fix With AIThis is a comment left during a code review.
Path: CHANGELOG.md
Line: 31
Comment:
Missing CHANGELOG entry for v0.3.2
The `package.json` was at version `0.3.2` before this PR (confirmed in PR description: "Previous: 0.3.2"), yet there is no `## [0.3.2]` section in `CHANGELOG.md`. The history jumps directly from `[0.3.1]` to `[0.4.0]`, leaving the patch release undocumented. If `0.3.2` contained meaningful changes, they should be recorded here to maintain an accurate audit trail.
How can I resolve this? If you propose a fix, please make it concise. |
||
|
|
||
| ### Documentation & Blog | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Extra blank lines before new section
Four consecutive blank lines appear before the
## [0.4.0]heading (lines 8–11), whereas the rest of the file uses a single blank line between sections. Consider trimming these to be consistent with the rest of the file.Prompt To Fix With AI
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!