Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 11 minutes and 56 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (5)
📝 WalkthroughWalkthroughAdds Airgapped Edition docs and updates navigation: introduces two new upgrade guides (Docker and Kubernetes), adds a collapsed "Airgapped Edition" submenu under Self-hosting → Manage → Update Plane, and revises airgapped eligibility/badge and deployment-methods content across methods/requirements pages. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In
`@docs/self-hosting/manage/update-plane/airgapped-edition/update-airgapped-docker.md`:
- Around line 1-4: The frontmatter for the markdown page is missing the required
keywords field; update the YAML frontmatter (the block containing title and
description in the file) to include a keywords property (e.g., keywords:
["airgapped", "docker", "upgrade", "plane"]) so the page conforms to
docs/**/*.md guidelines; ensure the keywords line is added inside the existing
--- frontmatter block alongside title and description and formatted as a YAML
list or comma-separated string.
In
`@docs/self-hosting/manage/update-plane/airgapped-edition/update-airgapped-kubernetes.md`:
- Around line 1-4: The frontmatter for the Markdown page is missing the required
keywords field; update the YAML frontmatter at the top of the file (the block
containing title and description) to include a keywords key with an array or
comma-separated list of relevant terms (e.g., keywords: ["airgapped", "upgrade",
"kubernetes"]) so the frontmatter contains title, description, and keywords as
required.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: f14e7600-92f3-45ad-899c-31bcf35e5ae5
📒 Files selected for processing (3)
docs/.vitepress/config.mtsdocs/self-hosting/manage/update-plane/airgapped-edition/update-airgapped-docker.mddocs/self-hosting/manage/update-plane/airgapped-edition/update-airgapped-kubernetes.md
docs/self-hosting/manage/update-plane/airgapped-edition/update-airgapped-docker.md
Show resolved
Hide resolved
docs/self-hosting/manage/update-plane/airgapped-edition/update-airgapped-kubernetes.md
Show resolved
Hide resolved
mguptahub
approved these changes
Apr 1, 2026
There was a problem hiding this comment.
Actionable comments posted: 2
♻️ Duplicate comments (2)
docs/self-hosting/manage/update-plane/airgapped-edition/update-airgapped-docker.md (1)
1-4:⚠️ Potential issue | 🟠 MajorAdd required
keywordsto frontmatter.This page frontmatter is missing
keywords, which is required for docs pages.💡 Proposed fix
--- title: Upgrade Airgapped Edition (Docker) description: Upgrade your airgapped Plane instance running on Docker by cloning images, replacing configuration files, and uploading a new license. +keywords: airgapped, docker, upgrade, self-hosting, plane ---As per coding guidelines:
docs/**/*.md: Every markdown page requires frontmatter with title, description, and keywords fields.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/self-hosting/manage/update-plane/airgapped-edition/update-airgapped-docker.md` around lines 1 - 4, The page frontmatter is missing the required YAML key "keywords"; update the frontmatter at the top of the file (where "title" and "description" are declared) to add a "keywords:" entry containing an array or comma-separated list of relevant keywords (e.g., keywords: ["airgapped", "docker", "upgrade"]) so the frontmatter includes title, description, and keywords; ensure the new "keywords" key follows the existing frontmatter format exactly.docs/self-hosting/manage/update-plane/airgapped-edition/update-airgapped-kubernetes.md (1)
1-4:⚠️ Potential issue | 🟠 MajorFrontmatter is incomplete: missing
keywords.Please add
keywordsso this page matches required docs frontmatter schema.💡 Proposed fix
--- title: Upgrade Airgapped Edition on Kubernetes description: Upgrade your airgapped Plane instance running on Kubernetes by cloning images, updating the Helm chart, and redeploying. +keywords: airgapped, kubernetes, helm, upgrade, self-hosting, plane ---As per coding guidelines:
docs/**/*.md: Every markdown page requires frontmatter with title, description, and keywords fields.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/self-hosting/manage/update-plane/airgapped-edition/update-airgapped-kubernetes.md` around lines 1 - 4, The frontmatter at the top of the Markdown (the YAML block containing title and description) is missing the required keywords field; update the frontmatter in the "Upgrade Airgapped Edition on Kubernetes" page by adding a keywords key with an array of relevant terms (e.g., ["airgapped", "kubernetes", "upgrade", "plane"]) so the frontmatter contains title, description, and keywords and conforms to the docs schema.
🧹 Nitpick comments (1)
docs/self-hosting/manage/update-plane/airgapped-edition/update-airgapped-kubernetes.md (1)
50-52: Consider adding the concrete Helm redeploy command.Step 4 says to redeploy but doesn’t include the actual command, which makes the update flow less actionable.
💡 Suggested addition
4. Once the Helm chart and `values.yaml` file are updated, redeploy the Helm release in your Kubernetes cluster to complete the update. + + ```bash + helm upgrade plane-app plane-enterprise-<chart_version>.tgz \ + --install \ + --namespace plane \ + -f values.yaml \ + --wait + ```🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/self-hosting/manage/update-plane/airgapped-edition/update-airgapped-kubernetes.md` around lines 50 - 52, Add a concrete Helm redeploy command to Step 4 so users can follow the update flow; insert a ready-to-run example using the helm upgrade invocation referencing the release name and chart (e.g., helm upgrade plane-app plane-enterprise-<chart_version>.tgz --install --namespace plane -f values.yaml --wait) and ensure the command is placed immediately after the sentence that instructs to "redeploy the Helm release" and before "Verify the upgrade by checking the version in your Plane application."
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs/self-hosting/methods/airgapped-edition-kubernetes.md`:
- Line 10: The info callout contains a duplicated word "for for" in the sentence
starting "Airgapped deployments are available exclusively for for Enterprise
Grid..."; edit that sentence to remove the extra "for" so it reads "...available
exclusively for Enterprise Grid customers..." and ensure the surrounding
punctuation and link to the sales email remain unchanged.
In `@docs/self-hosting/methods/airgapped-edition.md`:
- Line 10: The eligibility sentence contains a duplicated word "for" in the
airgapped notice; update the string "Airgapped deployments are available
exclusively for for Enterprise Grid customers with a minimum commitment of 100
seats." to remove the extra "for" so it reads "...available exclusively for
Enterprise Grid customers..." (locate and edit the line containing that exact
sentence in the airgapped-edition.md content).
---
Duplicate comments:
In
`@docs/self-hosting/manage/update-plane/airgapped-edition/update-airgapped-docker.md`:
- Around line 1-4: The page frontmatter is missing the required YAML key
"keywords"; update the frontmatter at the top of the file (where "title" and
"description" are declared) to add a "keywords:" entry containing an array or
comma-separated list of relevant keywords (e.g., keywords: ["airgapped",
"docker", "upgrade"]) so the frontmatter includes title, description, and
keywords; ensure the new "keywords" key follows the existing frontmatter format
exactly.
In
`@docs/self-hosting/manage/update-plane/airgapped-edition/update-airgapped-kubernetes.md`:
- Around line 1-4: The frontmatter at the top of the Markdown (the YAML block
containing title and description) is missing the required keywords field; update
the frontmatter in the "Upgrade Airgapped Edition on Kubernetes" page by adding
a keywords key with an array of relevant terms (e.g., ["airgapped",
"kubernetes", "upgrade", "plane"]) so the frontmatter contains title,
description, and keywords and conforms to the docs schema.
---
Nitpick comments:
In
`@docs/self-hosting/manage/update-plane/airgapped-edition/update-airgapped-kubernetes.md`:
- Around line 50-52: Add a concrete Helm redeploy command to Step 4 so users can
follow the update flow; insert a ready-to-run example using the helm upgrade
invocation referencing the release name and chart (e.g., helm upgrade plane-app
plane-enterprise-<chart_version>.tgz --install --namespace plane -f values.yaml
--wait) and ensure the command is placed immediately after the sentence that
instructs to "redeploy the Helm release" and before "Verify the upgrade by
checking the version in your Plane application."
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 5245084c-7941-4ed1-87ec-8e0ad966f285
📒 Files selected for processing (6)
docs/.vitepress/config.mtsdocs/self-hosting/manage/update-plane/airgapped-edition/update-airgapped-docker.mddocs/self-hosting/manage/update-plane/airgapped-edition/update-airgapped-kubernetes.mddocs/self-hosting/methods/airgapped-edition-kubernetes.mddocs/self-hosting/methods/airgapped-edition.mddocs/self-hosting/methods/airgapped-requirements.md
🚧 Files skipped from review as they are similar to previous changes (2)
- docs/self-hosting/methods/airgapped-requirements.md
- docs/.vitepress/config.mts
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Type of Change
Screenshots and Media (if applicable)
Test Scenarios
References
Summary by CodeRabbit