Release 0.18.0-rc.4 (ai-env-changed)

[wwwy3y3]

Release 0.18.0-rc.4

Summary by CodeRabbit

• Chores
  • Updated the release versions for the product, AI service, and UI components so that users benefit from the latest configurations and resources.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This pull request updates version numbers in the Docker configuration. In the docker/.env.example file, values for WREN_PRODUCT_VERSION, WREN_AI_SERVICE_VERSION, and WREN_UI_VERSION have been incremented. Additionally, the constant WREN_PRODUCT_VERSION in wren-launcher/utils/docker.go was updated to construct URLs that reference the new version.

Changes

Files	Change Summary
docker/.env.example	Updated WREN_PRODUCT_VERSION from 0.18.0-rc.3 to 0.18.0-rc.4, WREN_AI_SERVICE_VERSION from 0.18.1 to 0.18.2, and WREN_UI_VERSION from 0.23.3 to 0.23.4.
wren-launcher/utils/docker.go	Updated the constant WREN_PRODUCT_VERSION from "0.18.0-rc.3" to "0.18.0-rc.4", ensuring the URLs constructed for configuration and environment files use the new version.

Possibly related PRs

• release 0.16.0 #1405: The changes in the main PR are related to the same constant WREN_PRODUCT_VERSION being updated in both PRs, indicating a direct connection at the code level.
• Release 0.15.3-rc.1 #1255: The changes in the main PR are related to the updates of the WREN_PRODUCT_VERSION constant in both the docker/.env.example file and the wren-launcher/utils/docker.go file, indicating a direct connection at the code level.
• release 0.15.2-rc.1 #1238: The changes in the main PR are directly related to the updates of the WREN_PRODUCT_VERSION constant in both the docker/.env.example and wren-launcher/utils/docker.go files, reflecting the same version increment.

Suggested reviewers

• onlyjackfrost

Poem

I'm a bunny with a joyful hop,
As version numbers rise nonstop.
From rc.3 to rc.4, I cheer,
With updated code so bright and clear.
Hop along through Docker's door,
Celebrating changes forevermore! 🐇

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between cf67b00 and 5db5f11.

📒 Files selected for processing (2)

• docker/.env.example (1 hunks)
• wren-launcher/utils/docker.go (1 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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 docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.