Skip to content

Conversation

@devin-ai-integration
Copy link
Contributor

@devin-ai-integration devin-ai-integration bot commented Jun 24, 2025

Add missing CLI releases v0.0.150, v0.0.151, v0.0.152 to changelog

Summary

This PR addresses the comment in PR #206 to add the missing CLI release versions between v0.0.149 and v0.0.153. I identified that three CLI releases were missing from the documentation changelog and added them with their complete release details:

  • v0.0.152 (June 24, 2025): Project directory protection and hot reload fixes
  • v0.0.151 (June 18, 2025): Docker hostname compatibility and deploy status improvements
  • v0.0.150 (June 13, 2025): Groq patch module addition and JSONC parsing fixes

The information was extracted from the official CLI repository changelog and formatted to match the existing documentation changelog structure with Callout components and proper categorization.

Review & Testing Checklist for Human

  • Verify release information accuracy: Cross-check the added release details against the official CLI changelog to ensure no transcription errors in PR numbers, dates, or descriptions
  • Test changelog page rendering: Navigate to /Changelog/cli on the deployed preview to confirm the new entries render correctly with proper formatting and Callout components
  • Validate chronological order: Confirm versions are in correct reverse chronological order (v0.0.153 → v0.0.152 → v0.0.151 → v0.0.150 → v0.0.149)
  • Test PR links: Click through the GitHub PR links in the new entries to verify they point to the correct CLI repository pull requests

Recommended test plan: Deploy the preview, navigate to the CLI changelog page, scroll through the newly added versions, and spot-check a few PR links to ensure everything displays and functions correctly.


Diagram

%%{ init : { "theme" : "default" }}%%
graph TD
    A["content/Changelog/cli.mdx"]:::major-edit --> B["v0.0.153 (existing)"]:::context
    A --> C["v0.0.152 (added)"]:::major-edit
    A --> D["v0.0.151 (added)"]:::major-edit  
    A --> E["v0.0.150 (added)"]:::major-edit
    A --> F["v0.0.149 (existing)"]:::context
    
    G["CLI repo CHANGELOG.md"]:::context --> H["Source for release details"]:::context
    G --> C
    G --> D
    G --> E
    
    subgraph Legend
        L1["Major Edit"]:::major-edit
        L2["Minor Edit"]:::minor-edit
        L3["Context/No Edit"]:::context
    end
    
    classDef major-edit fill:#90EE90
    classDef minor-edit fill:#87CEEB  
    classDef context fill:#FFFFFF
Loading

Notes

  • Information was sourced directly from the official CLI repository changelog to ensure accuracy
  • Maintained exact formatting consistency with existing changelog entries including Callout components and bold category prefixes
  • Changes committed to existing PR branch rather than creating a new PR as requested
  • Link to Devin run: https://app.devin.ai/sessions/f2da302970874df6887d3c255de7b60e
  • Requested by: jhaynie (@jhaynie)

Co-Authored-By: unknown <>
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jun 24, 2025

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Join our Discord community for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@cloudflare-workers-and-pages
Copy link

cloudflare-workers-and-pages bot commented Jun 24, 2025

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
docs 7a7abb8 Commit Preview URL Jun 30 2025, 09:33 PM

Copy link
Member

@jhaynie jhaynie left a comment

Choose a reason for hiding this comment

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

please add missing releases

Copy link
Member

@jhaynie jhaynie left a comment

Choose a reason for hiding this comment

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

merge with main and resolve conflicts

**Changes:**
- **Changed**: When running dev mode, make sure we have a .env.development file ([#400](https://github.com/agentuity/cli/pull/400))

## v0.0.149
Copy link
Member

Choose a reason for hiding this comment

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

add missing release versions

- Added v0.0.152 with project directory protection and hot reload fixes
- Added v0.0.151 with docker hostname compatibility and deploy status improvements
- Added v0.0.150 with groq patch module and JSONC parsing fixes
- Maintains chronological order with proper formatting and PR links

Co-Authored-By: jhaynie@agentuity.com <jhaynie@gmail.com>
Copy link
Member

@jhaynie jhaynie left a comment

Choose a reason for hiding this comment

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

merge with main and resolve conflicts

- Main branch already contains all the releases I added (v0.0.150, v0.0.151, v0.0.152)
- Plus newer releases v0.0.154 and v0.0.155 that were added after my original PR
- Accepting the complete and up-to-date changelog from main branch

Co-Authored-By: jhaynie@agentuity.com <jhaynie@gmail.com>
@jhaynie jhaynie closed this Jun 30, 2025
@jhaynie jhaynie deleted the devin/1750781802-update-changelog-v0.0.153 branch June 30, 2025 21:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants