Skip to content

chore(release): v0.4.0#262

Merged
rubenmarcus merged 1 commit intomainfrom
release/v0.4.0
Mar 5, 2026
Merged

chore(release): v0.4.0#262
rubenmarcus merged 1 commit intomainfrom
release/v0.4.0

Conversation

@rubenmarcus
Copy link
Copy Markdown
Member

Release v0.4.0

Added

Fixed

Changed

Version bump

  • Previous: 0.3.2
  • New: 0.4.0
  • Type: minor

What happens when this PR is merged

  1. Git tag v0.4.0 will be created
  2. GitHub Release will be published
  3. Package will be published to npm with latest tag

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Mar 5, 2026

✔️ Bundle Size Analysis

Metric Value
Base 2425.03 KB
PR 2425.03 KB
Diff 0 KB (0%)
Bundle breakdown
156K	dist/auth
32K	dist/automation
4.0K	dist/cli.d.ts
4.0K	dist/cli.d.ts.map
20K	dist/cli.js
12K	dist/cli.js.map
568K	dist/commands
28K	dist/config
4.0K	dist/index.d.ts
4.0K	dist/index.d.ts.map
4.0K	dist/index.js
4.0K	dist/index.js.map
896K	dist/integrations
84K	dist/llm
900K	dist/loop
188K	dist/mcp
32K	dist/presets
92K	dist/setup
40K	dist/skills
392K	dist/sources
76K	dist/ui
144K	dist/utils
336K	dist/wizard

@rubenmarcus rubenmarcus merged commit 34526e5 into main Mar 5, 2026
15 checks passed
@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps bot commented Mar 5, 2026

Greptile Summary

This is a standard release PR that bumps package.json from 0.3.20.4.0 and adds the corresponding CHANGELOG.md entry documenting the new features, fixes, and changes shipped in this minor release.

Key observations:

  • The version bump from 0.3.2 to 0.4.0 is appropriate given the scope of features added (Figma integration enhancements, new --max-cost flag, unified GitHub & Linear task management).
  • The CHANGELOG.md entry is well-structured and references the relevant PR numbers.
  • [0.3.2] is missing from the changelog — the file jumps directly from [0.3.1] to [0.4.0]. Since package.json was at 0.3.2 before this PR, that patch release was never documented.
  • Four consecutive blank lines appear before the ## [0.4.0] heading, which is inconsistent with the single-blank-line convention used elsewhere in the file.

Confidence Score: 4/5

  • This PR is safe to merge; changes are limited to a version bump and changelog update with no runtime code modifications.
  • Only two documentation/metadata files are changed. The version bump is correct and the changelog is accurate. Two style/documentation quality issues keep it from a perfect 5: the missing [0.3.2] changelog entry and extra blank lines before the new section are valid but non-critical quality gaps.
  • No files require special attention — all changes are in CHANGELOG.md and package.json.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[PR #262 merged] --> B[Git tag v0.4.0 created]
    B --> C[GitHub Release published]
    C --> D[npm publish with 'latest' tag]
    D --> E[Users receive ralph-starter@0.4.0]

    subgraph "Version history"
        F["0.3.1 (documented)"] --> G["0.3.2 (undocumented patch)"]
        G --> H["0.4.0 (this release)"]
    end
Loading

Last reviewed commit: 7519309

### Changed
- add context-builder and task-executor tests (#250)

## [0.3.1] - 2026-02-19
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.

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.

Prompt To Fix With AI
This 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.




## [0.4.0] - 2026-03-05
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.

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.

Suggested change
## [0.4.0] - 2026-03-05
## [0.4.0] - 2026-03-05
Prompt To Fix With AI
This is a comment left during a code review.
Path: CHANGELOG.md
Line: 12

Comment:
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.

```suggestion
## [0.4.0] - 2026-03-05
```

How can I resolve this? If you propose a fix, please make it concise.

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!

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Mar 5, 2026

v0.4.0 has been released!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant