release: 0.16.0-rc.1

[onlyjackfrost]

release: 0.16.0-rc.1

Summary by CodeRabbit

• Chores
  • Upgraded core component versions used in our container deployments.
  • Refreshed configuration references to align with the latest product release candidate.

[coderabbitai]

Walkthrough

This pull request updates version numbers across two files. In docker/.env.example, several WREN-related version variables and the IBIS server version are incremented. In wren-launcher/utils/docker.go, the constant WREN_PRODUCT_VERSION is updated to include a release candidate suffix, which adjusts the URLs that incorporate this version. These modifications align the referenced versions across configuration and launcher utilities.

Changes

File(s)	Change Summary
docker/.env.example	Updated version numbers: - WREN_PRODUCT_VERSION: 0.15.4 → 0.16.0 - WREN_ENGINE_VERSION: 0.14.3 → 0.14.5 - WREN_AI_SERVICE_VERSION: 0.15.18 → 0.16.1 - IBIS_SERVER_VERSION: 0.14.3 → 0.14.5 - WREN_UI_VERSION: 0.20.2 → 0.21.0
wren-launcher/utils/docker.go	Updated constant WREN_PRODUCT_VERSION from "0.15.4" to "0.16.0-rc.1", thereby updating associated URL constructions.

Possibly related PRs

• release 0.15.4-rc.1 #1357: Updates the WREN_PRODUCT_VERSION variable, aligning directly with the changes in this PR.
• chore(wren-ui): update release image flow and revert package.json version #1350: Modifies the WREN_PRODUCT_VERSION in docker/.env.example, paralleling the update here.
• release oss 0.15.3 #1260: Implements coordinated updates for WREN_PRODUCT_VERSION across multiple files, reflecting code-level connections to this PR.

Suggested reviewers

• wwwy3y3

Poem

In my burrow of code so bright,
New versions hop into the light.
Each update a carrot, crisp and neat,
Making our binaries sing a beat.
With twitching nose and joyful hops,
I celebrate these changes as my heart pops! 🐇

Warning

There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure.

🔧 golangci-lint (1.62.2)

level=error msg="Running error: context loading failed: no go files to analyze: running go mod tidy may solve the problem"

Tip

⚡🧪 Multi-step agentic review comment chat (experimental)

• We're introducing multi-step agentic chat in review comments. This experimental feature enhances review discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments.
  - To enable this feature, set early_access to true under in the settings.

---

📜 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 2a7a9cb and 8ea3c23.

📒 Files selected for processing (2)

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

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: Analyze (javascript-typescript)
• GitHub Check: Analyze (go)

🔇 Additional comments (4)

wren-launcher/utils/docker.go (2)

27-27: Version properly updated to 0.16.0-rc.1.

The constant WREN_PRODUCT_VERSION has been correctly updated to the new release candidate version "0.16.0-rc.1". This change ensures that all GitHub URLs on lines 28-30 will now reference files from this specific version tag.

---

28-30: URLs now reference the new version.

The URLs for Docker compose YAML, .env example, and AI service configuration are now automatically updated to reference the 0.16.0-rc.1 tag through the constant reference. This ensures that launcher downloads the correct configuration files for this release.

docker/.env.example (2)

24-27: Component versions updated appropriately.

The version numbers for individual components have been updated:

• WREN_ENGINE_VERSION: 0.14.3 → 0.14.5
• WREN_AI_SERVICE_VERSION: 0.15.18 → 0.16.1
• IBIS_SERVER_VERSION: 0.14.3 → 0.14.5
• WREN_UI_VERSION: 0.20.2 → 0.21.0

These changes reflect the version increments expected for a new release.

---

23-27:

Details

❓ Verification inconclusive

Version inconsistency between files.

There's a discrepancy between the version in this file (WREN_PRODUCT_VERSION=0.16.0) and the version in wren-launcher/utils/docker.go (WREN_PRODUCT_VERSION="0.16.0-rc.1"). The .env file doesn't include the release candidate suffix.

Is this intentional? If both should match exactly, consider updating this file to include the "-rc.1" suffix as well.

---

🏁 Script executed:

#!/bin/bash
# Check version references across files
echo "Version in docker/.env.example:"
grep "WREN_PRODUCT_VERSION" docker/.env.example

echo "Version in wren-launcher/utils/docker.go:"
grep "WREN_PRODUCT_VERSION" wren-launcher/utils/docker.go

# Check if other files reference these versions
echo "Other files that might reference the version:"
rg "0.16.0" --type-not binary | grep -v "docker/.env.example" | grep -v "wren-launcher/utils/docker.go"

Length of output: 992

---

Version Mismatch Detected – Please Verify Intentionality

• The Docker environment file (docker/.env.example) sets WREN_PRODUCT_VERSION=0.16.0, while in wren-launcher/utils/docker.go the version is defined as "0.16.0-rc.1".
• If these should be identical, please update docker/.env.example by appending the -rc.1 suffix (or adjust the code accordingly) to ensure consistency.
• Note: The additional check for references to "0.16.0" produced an error regarding binary file types, so it might be worthwhile to manually verify that no other relevant files are affected by this discrepancy.

✨ 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 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.