Skip to content

realtime update#2825

Open
eldadfux wants to merge 1 commit intomainfrom
feat-realtime-update
Open

realtime update#2825
eldadfux wants to merge 1 commit intomainfrom
feat-realtime-update

Conversation

@eldadfux
Copy link
Member

@eldadfux eldadfux commented Mar 21, 2026

What does this PR do?

(Provide a description of what this PR does.)

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

Related PRs and Issues

(If this PR is related to any other PR or resolves any issue or related to any issue link all related PR and issues here.)

Have you read the Contributing Guidelines on issues?

(Write your answer here.)

Summary by CodeRabbit

  • Documentation
    • Announced Realtime usage limits and billing enforcement for Appwrite Cloud beginning April 15, 2026, with plan-specific quotas for monthly messages (Free 2M, Pro 6M), concurrent connections (Free 250, Pro 500), and message sizes (Free 256 KB, Pro 3 MB).

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 21, 2026

Walkthrough

A new changelog entry document is added at src/routes/changelog/(entries)/2026-03-19.markdoc that announces Appwrite Cloud will begin enforcing Realtime usage limits and billing starting April 15, 2026. The entry specifies plan-specific limits for monthly messages (Free: 2M, Pro: 6M), concurrent connections (Free: 250, Pro: 500), and message sizes (Free: 256 KB, Pro: 3 MB), and notes that Realtime bandwidth counts toward the plan's general bandwidth allowance. The document includes calls to action with links to the billing console, pricing page, and documentation on Realtime queries.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Title check ❓ Inconclusive The title 'realtime update' is vague and generic, using non-descriptive terminology that does not convey meaningful information about the specific changes. Use a more specific title that describes the actual change, such as 'Add changelog entry for Realtime usage limits enforcement' or 'Announce Realtime billing enforcement starting April 15, 2026'.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat-realtime-update

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

Comment @coderabbitai help to get the list of available commands and usage tips.

@greptile-apps
Copy link
Contributor

greptile-apps bot commented Mar 21, 2026

Greptile Summary

This PR adds a new changelog entry (2026-03-19.markdoc) announcing that Appwrite Cloud will begin actively enforcing Realtime usage limits and billing starting April 15, 2026, covering messages, concurrent connections, and max message size.

Issues found:

  • The filename 2026-03-19.markdoc does not match the frontmatter date: 2026-03-23. Every other entry in the changelog directory follows the convention where the filename and date field are identical. This mismatch may cause incorrect ordering or keying of the entry on the changelog page.
  • Minor grammar error on line 13: "Pro include 6M messages/month" should be "Pro includes 6M messages/month" to match subject-verb agreement with the rest of the sentence.

Confidence Score: 3/5

  • Safe to merge after fixing the filename/date mismatch, which could cause incorrect changelog ordering.
  • The change is purely a documentation/content file with no code logic. However, the date mismatch between the filename and the frontmatter date field is a meaningful inconsistency that breaks the established naming convention across all other entries and could affect how the page is rendered or sorted.
  • src/routes/changelog/(entries)/2026-03-19.markdoc — filename and frontmatter date are out of sync.

Important Files Changed

Filename Overview
src/routes/changelog/(entries)/2026-03-19.markdoc New changelog entry announcing Realtime usage limit enforcement starting April 15, 2026; has a mismatch between the filename date (2026-03-19) and the frontmatter date field (2026-03-23), and a minor grammar error ("Pro include" should be "Pro includes").

Last reviewed commit: "realtime update"

---
layout: changelog
title: "Appwrite Cloud: Realtime usage limits and billing enforcement"
date: 2026-03-23
Copy link
Contributor

Choose a reason for hiding this comment

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

P2 Frontmatter date doesn't match filename

The file is named 2026-03-19.markdoc, which conventionally represents March 19, 2026, but the date field in the frontmatter is set to 2026-03-23 (March 23). Every other entry in this directory follows the convention of matching the filename to the frontmatter date (e.g., 2025-03-19.markdoc has date: 2025-03-19). If the changelog is sorted or keyed by the date field, this file will appear to belong to March 23, not March 19, leading to confusing ordering. The date should be corrected to match the filename, or the filename should be renamed to 2026-03-23.markdoc.

Suggested change
date: 2026-03-23
date: 2026-03-19


**Realtime limits:**

- **Messages:** Free plan includes 2M messages/month; Pro include 6M messages/month. Additional messages are billed at $2.50 per 1M.
Copy link
Contributor

Choose a reason for hiding this comment

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

P2 Subject-verb agreement error

"Pro include 6M messages/month" is missing the third-person singular 's'. It should be "Pro includes 6M messages/month" to be grammatically correct and consistent with "Free plan includes" at the start of the same sentence.

Suggested change
- **Messages:** Free plan includes 2M messages/month; Pro include 6M messages/month. Additional messages are billed at $2.50 per 1M.
- **Messages:** Free plan includes 2M messages/month; Pro includes 6M messages/month. Additional messages are billed at $2.50 per 1M.

Copy link
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

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@src/routes/changelog/`(entries)/2026-03-19.markdoc:
- Line 13: Fix the subject-verb agreement in the changelog entry by replacing
"Pro include 6M messages/month" with "Pro includes 6M messages/month" so the
verb agrees with the singular subject "Pro" in the sentence that reads
"**Messages:** Free plan includes 2M messages/month; Pro include 6M
messages/month. Additional messages are billed at $2.50 per 1M."

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: b9243f4d-e52a-4fc7-b0fa-121bd2f62788

📥 Commits

Reviewing files that changed from the base of the PR and between 404ca84 and fe4bca7.

📒 Files selected for processing (1)
  • src/routes/changelog/(entries)/2026-03-19.markdoc


**Realtime limits:**

- **Messages:** Free plan includes 2M messages/month; Pro include 6M messages/month. Additional messages are billed at $2.50 per 1M.
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Fix subject-verb agreement.

The phrase "Pro include 6M messages/month" should be "Pro includes 6M messages/month" to maintain proper subject-verb agreement.

📝 Proposed fix
-- **Messages:** Free plan includes 2M messages/month; Pro include 6M messages/month. Additional messages are billed at $2.50 per 1M.
+- **Messages:** Free plan includes 2M messages/month; Pro includes 6M messages/month. Additional messages are billed at $2.50 per 1M.
📝 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
- **Messages:** Free plan includes 2M messages/month; Pro include 6M messages/month. Additional messages are billed at $2.50 per 1M.
- **Messages:** Free plan includes 2M messages/month; Pro includes 6M messages/month. Additional messages are billed at $2.50 per 1M.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@src/routes/changelog/`(entries)/2026-03-19.markdoc at line 13, Fix the
subject-verb agreement in the changelog entry by replacing "Pro include 6M
messages/month" with "Pro includes 6M messages/month" so the verb agrees with
the singular subject "Pro" in the sentence that reads "**Messages:** Free plan
includes 2M messages/month; Pro include 6M messages/month. Additional messages
are billed at $2.50 per 1M."

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.

1 participant