Skip to content

Update console#9792

Merged
abnegate merged 1 commit into1.7.xfrom
chore-bump-console
May 18, 2025
Merged

Update console#9792
abnegate merged 1 commit into1.7.xfrom
chore-bump-console

Conversation

@abnegate
Copy link
Copy Markdown
Member

@abnegate abnegate commented May 18, 2025 •
edited by coderabbitai bot
Loading

What does this PR do?

(Provide a description of what this PR does and why it's needed.)

Test Plan

(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work. Screenshots may also be helpful.)

Related PRs and Issues

  • (Related PR or issue)

Checklist

  • Have you read the Contributing Guidelines on issues?
  • If the PR includes a change to an API's metadata (desc, label, params, etc.), does it also include updated API specs and example docs?

Summary by CodeRabbit

  • Chores
    • Updated the Docker image for the console service to version 6.0.0.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented May 18, 2025 •
edited
Loading

Walkthrough

The changes update the Docker image version for the appwrite-console service in both the Docker Compose configuration and a related template file. The image tag is incremented from a 5.x release candidate to the 6.0.0 version, with no other modifications to configuration or service properties.

Changes

File(s) Change Summary
app/views/install/compose.phtml Updated the appwrite-console Docker image tag from ${ORG}/appwrite-console:5.3.0-sites-rc.51 to ${ORG}/appwrite-console:6.0.0.
docker-compose.yml Updated the appwrite-console Docker image tag from appwrite/console:5.3.0-sites-rc.43 to appwrite/console:6.0.0.

Poem

Up hops the console, version six in tow,
Docker tags are changing, onward we go!
New image on the horizon, fresh as morning dew,
Compose files updated, the future feels new.
With every small version, the rabbit leaps high—
Code and containers, reaching for the sky!
🐇✨

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
🪧 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? Create a ticket on our support page 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 docstrings to generate docstrings for this 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.

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.

@github-actions
Copy link
Copy Markdown

github-actions bot commented May 18, 2025

Security Scan Results for PR

Docker Image Scan Results

Package Version Vulnerability Severity
binutils 2.42-r0 CVE-2025-0840 HIGH
libexpat 2.6.4-r0 CVE-2024-8176 HIGH
libxml2 2.12.7-r0 CVE-2024-56171 HIGH
libxml2 2.12.7-r0 CVE-2025-24928 HIGH
libxml2 2.12.7-r0 CVE-2025-27113 HIGH
libxml2 2.12.7-r0 CVE-2025-32414 HIGH
libxml2 2.12.7-r0 CVE-2025-32415 HIGH
sqlite-libs 3.45.3-r1 CVE-2025-29087 HIGH
xz 5.6.2-r0 CVE-2025-31115 HIGH
xz-libs 5.6.2-r0 CVE-2025-31115 HIGH
golang.org/x/crypto v0.31.0 CVE-2025-22869 HIGH

Source Code Scan Results

🎉 No vulnerabilities found!

coderabbitai[bot]
coderabbitai bot reviewed May 18, 2025
View reviewed changes
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between 58d0862 and b3170df.

📒 Files selected for processing (2)
  • app/views/install/compose.phtml (1 hunks)
  • docker-compose.yml (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (20)
  • GitHub Check: E2E Service Test (Migrations)
  • GitHub Check: E2E Service Test (Messaging)
  • GitHub Check: E2E Service Test (Tokens)
  • GitHub Check: E2E Service Test (Users)
  • GitHub Check: E2E Service Test (Sites)
  • GitHub Check: E2E Service Test (Teams)
  • GitHub Check: E2E Service Test (Storage)
  • GitHub Check: E2E Service Test (Projects)
  • GitHub Check: E2E Service Test (Locale)
  • GitHub Check: E2E Service Test (FunctionsSchedule)
  • GitHub Check: E2E Service Test (GraphQL)
  • GitHub Check: E2E Service Test (Console)
  • GitHub Check: E2E Service Test (Health)
  • GitHub Check: E2E Service Test (Functions)
  • GitHub Check: E2E Service Test (Databases)
  • GitHub Check: E2E Service Test (Account)
  • GitHub Check: E2E Service Test (Avatars)
  • GitHub Check: E2E Service Test (Dev Keys)
  • GitHub Check: E2E General Test
  • GitHub Check: Unit Test
🔇 Additional comments (1)
docker-compose.yml (1)

216-216: Approve console image tag bump
The appwrite-console service image tag has been correctly updated to 6.0.0, aligning with the new release. Please verify that this version is available on Docker Hub and update any related upgrade or release documentation (e.g., README, CHANGELOG) to reflect this bump.

app/views/install/compose.phtml
Comment on lines 178 to 181
<<: *x-logging
container_name: appwrite-console
image: <?php echo $organization; ?>/console:5.3.0-sites-rc.51
image: <?php echo $organization; ?>/console:6.0.0
restart: unless-stopped
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot May 18, 2025

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Use dynamic version parameter for console image
The console service currently hardcodes 6.0.0. To maintain consistency with other services and leverage the $version parameter provided by the installer, refactor this to:

-    image: <?php echo $organization; ?>/console:6.0.0
+    image: <?php echo $organization; ?>/console:<?php echo $version; ?>

This change ensures the template picks up the correct release tag automatically.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
<<: *x-logging
container_name: appwrite-console
image: <?php echo $organization; ?>/console:5.3.0-sites-rc.51
image: <?php echo $organization; ?>/console:6.0.0
restart: unless-stopped
<<: *x-logging
container_name: appwrite-console
image: <?php echo $organization; ?>/console:<?php echo $version; ?>
restart: unless-stopped
🤖 Prompt for AI Agents 
In app/views/install/compose.phtml around lines 178 to 181, the console image
version is hardcoded as "6.0.0". Replace this static version with the dynamic
$version parameter used elsewhere in the installer to ensure the image tag
updates automatically with the release version. Modify the image line to use the
$version variable instead of the fixed string.

@github-actions
Copy link
Copy Markdown

github-actions bot commented May 18, 2025

✨ Benchmark results

  • Requests per second: 947
  • Requests with 200 status code: 170,544
  • P99 latency: 0.199378268

⚡ Benchmark Comparison

Metric This PR Latest version
RPS 947 1,239
200 170,544 223,052
P99 0.199378268 0.146777314

@abnegate abnegate merged commit e4cf79c into 1.7.x May 18, 2025
38 checks passed
This was referenced Oct 21, 2025
Merged
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

1 more reviewer

@coderabbitai coderabbitai[bot] coderabbitai[bot] left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@abnegate