8000 Bump console to version 6.0.11 by stnguyen90 · Pull Request #9881 · appwrite/appwrite · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Bump console to version 6.0.11 #9881

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
May 23, 2025
Merged

Bump console to version 6.0.11 #9881

merged 1 commit into from
May 23, 2025

Conversation

stnguyen90
Copy link
Contributor
@stnguyen90 stnguyen90 commented May 23, 2025 •
edited by coderabbitai bot
Loading

What does this PR do?

Bump console to version 6.0.11

Test Plan

None

Related PRs and Issues

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 Compose configuration to use a newer version of the appwrite-console service.

@coderabbitai coderabbitai
Copy link
coderabbitai bot commented May 23, 2025 •
edited
Loading

Walkthrough

The image version for the appwrite-console service was updated from 6.0.8 to 6.0.11 in both the Docker Compose configuration and its related view template. No other service settings or configurations were changed.

Changes

File(s) Change Summary
app/views/install/compose.phtml Updated appwrite-console image tag from 6.0.8 to 6.0.11
docker-compose.yml Updated appwrite-console image tag from 6.0.8 to 6.0.11

Poem

A hop and a skip, a version anew,
Console refreshed, now 6.0.11 in view.
Compose lines updated, so crisp and so clean,
Docker dreams running, a seamless routine.
With every small change, our warren grows bright—
Hopping to progress, from morning till night! 🐇✨

Note

⚡️ AI Code Reviews for VS Code, Cursor, Windsurf

CodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback.
Learn more here.

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d8904af and 0ec7dcf.

📒 Files selected for processing (2)
  • app/views/install/compose.phtml (1 hunks)
  • docker-compose.yml (1 hunks)
🔇 Additional comments (2)
docker-compose.yml (1)

216-216: Update appwrite-console image tag to 6.0.11
The console service is now pinned to the latest 6.0.11 release, matching the intended version bump. No other settings were modified.

app/views/install/compose.phtml (1)

180-180: Align install template console image version to 6.0.11
The view template’s appwrite-console image tag has been updated to :6.0.11, keeping it in sync with the root Docker Compose configuration.

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.

@stnguyen90 stnguyen90 linked an issue May 23, 2025 that may be closed by this pull request
🐛 Bug Report: Failed to fetch #9862
Closed
2 tasks
@github-actions GitHub Actions
< 8000 span data-view-component="true"> Copy link

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!

@github-actions GitHub Actions
Copy link

✨ Benchmark results

  • Requests per second: 927
  • Requests with 200 status code: 166,947
  • P99 latency: 0.203069233

⚡ Benchmark Comparison

Metric This PR Latest version
RPS 927 1,155
200 166,947 207,932
P99 0.203069233 0.162654349

@stnguyen90 stnguyen90 marked this pull request as ready for review May 23, 2025 22:33
@EVDOG4LIFE EVDOG4LIFE self-requested a review May 23, 2025 23:00
@stnguyen90 stnguyen90 merged commit 7208729 into main May 23, 2025
38 checks passed
@stnguyen90 stnguyen90 deleted the chore-bump-console-6.0.11 branch May 23, 2025 23:00
@coderabbitai coderabbitai bot mentioned this pull request May 25, 2025
Merged
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@EVDOG4LIFE EVDOG4LIFE EVDOG4LIFE approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

🐛 Bug Report: Failed to fetch
2 participants
@stnguyen90 @EVDOG4LIFE
0