Skip to content

Development - #156

Merged
CodeMeAPixel merged 4 commits into
productionfrom
development
Oct 4, 2026
Merged

CodeMeAPixel merged 4 commits into
productionfrom
development

Conversation

@CodeMeAPixel

@CodeMeAPixel CodeMeAPixel commented Oct 3, 2026 •

Copy link
Copy Markdown
Contributor

Summary by CodeRabbit

  • Updates
    • Billing, store, product, and support-ticket links now point to updated billing-panel destinations. The Discord link has also been updated.
    • Dedicated server, game server, VPS, and object storage plans now use a consistent card layout.
    • CPU specifications recognize both vCPU and vCore descriptions.
  • Removals
    • AMD and Intel VPS pricing listings, plan filters, and purchase controls are no longer available, and their pages are no longer included in the sitemap.
    • The development-only billing diagnostic endpoint has been removed.
    • The node status page is no longer available; /nodes now redirects to the Looking Glass. The navigation and footer no longer link to the node status page.

@coderabbitai

coderabbitai Bot commented Oct 3, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

⚙️ Run configuration
  • Configuration used: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 7e407882-048d-46e9-868a-00fe06aaa304
📥 Commits

Reviewing files that changed from the base of the PR and between f34538d and bfcdb43.

📒 Files selected for processing (16)
  • app/nodes/page.tsx
  • next.config.mjs
  • packages/core/constants/links.ts
  • packages/core/constants/status-mapping.ts
  • packages/core/lib/spec-parser.ts
  • packages/core/lib/status.ts
  • packages/ui/components/Layouts/Dedicated/dedicated-hub.tsx
  • packages/ui/components/Layouts/Games/game-hub.tsx
  • packages/ui/components/Layouts/Home/services.tsx
  • packages/ui/components/Layouts/Nodes/nodes-client.tsx
  • packages/ui/components/Layouts/ObjectStorage/object-storage-hub.tsx
  • packages/ui/components/Layouts/VPS/vps-hub.tsx
  • packages/ui/components/Static/footer.tsx
  • packages/ui/components/Static/navigation.tsx
  • packages/ui/components/ui/plan-card.tsx
  • translations
 ______________________________________
< Be a super developer. Go home early. >
 --------------------------------------
  \
   \   (\__/)
       (•ㅅ•)
       /   づ

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration
  • Configuration used: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: aa992b58-ae9f-41c6-859f-e0ff2f6c629a
📥 Commits

Reviewing files that changed from the base of the PR and between f3a33e2 and f34538d.

📒 Files selected for processing (10)
  • .env.example
  • app/api/billing-debug/route.ts
  • app/sitemap.ts
  • packages/core/constants/links.ts
  • packages/core/constants/vps/amd.ts
  • packages/core/constants/vps/index.ts
  • packages/core/constants/vps/intel.ts
  • packages/core/lib/bytepay.ts
  • packages/ui/components/Layouts/Contact/contact.tsx
  • packages/ui/components/Layouts/VPS/vps-pricing.tsx
💤 Files with no reviewable changes (6)
  • packages/core/constants/vps/intel.ts
  • packages/core/constants/vps/amd.ts
  • packages/ui/components/Layouts/VPS/vps-pricing.tsx
  • app/api/billing-debug/route.ts
  • app/sitemap.ts
  • packages/core/constants/vps/index.ts

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.


📝 Walkthrough

Walkthrough

The change centralizes billing-panel URLs and updates BytePay and support links to use them. It removes the billing debug endpoint and static VPS plan data, pricing UI, and sitemap entries. The environment example now lists BytePay host and token settings.

Changes

Billing and VPS changes

Layer / File(s) Summary
Centralize billing URLs and remove debug endpoint
.env.example, packages/core/constants/links.ts, packages/core/lib/bytepay.ts, packages/ui/components/Layouts/Contact/contact.tsx, app/api/billing-debug/route.ts
The environment example replaces the previous settings with BYTEPAY_HOST and BYTEPAY_TOKEN. Billing links use the shared BILLING_URL; BytePay order URLs and the support ticket link use shared link constants. The billing debug route is deleted.
Remove static VPS pricing
packages/core/constants/vps/*, packages/ui/components/Layouts/VPS/vps-pricing.tsx, app/sitemap.ts
The AMD and Intel VPS constants and pricing component are deleted. The sitemap no longer includes /vps/amd or /vps/intel.

Priority: ➖ Normal

Estimated code review effort: 3 (Moderate) | ~20 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to f3453

No repository-supported merge-blocking issue was found. The changed support link’s authenticated destination could not be verified, so confirm it through normal checks before relying on ticket submissions.

Security Architecture Review

Security architecture risk: 🔵 Low · up to f3453

Billing and support navigation remain on the same billing host, with no new credential forwarding observed. Risk is limited mainly by uncertainty about whether the updated paths match the deployed billing panel.

Retained concerns
No architecture-level concerns identified.

Security review details

Security Blast Radius

  • inferred — A destination-contract error in the shared helper could affect order navigation across all four plan families, while the ticket-path change affects public support navigation. The inspected changes do not increase website-side privileges; the external panel's effective authority and downstream route behavior remain unverified.

Security Findings and Attack Paths

  • inferred — No introduced attacker-controlled destination or explicit credential-forwarding path was established in the reviewed billing-link changes. Dynamic category and product values were already interpolated into paths at the base revision; the PR changes the fixed path prefix, not their authority to select an origin. This conclusion does not establish the safety of unavailable external handlers.

Trust Boundaries and Controls

  • observed — The website continues to hand billing and ticket navigation to the same external HTTPS origin. The Contact anchor retains opener and referrer isolation. Authentication and authorization for the destination routes are not implemented by this link contract and cannot be assessed from its source.
🚥 Pre-merge checks | ✅ 3 | ❌ 1 | ❓ 1

❌ Failed checks (1 warning, 1 inconclusive)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 33.33% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 3 functions across 3 files. (1 skipped: 1… Write docstrings for the functions missing them to satisfy the coverage threshold.
Title check ❓ Inconclusive The title “Development” is too vague to identify the pull request’s changes. Replace it with a concise, specific title, such as “Remove static VPS pricing and update BytePay billing links.”
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage

Explanation

Docstring coverage is 33.33% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 3 functions across 3 files. (1 skipped: 1 unsupported.)

  • Fix all pre-merge checks with AI
✨ Finishing Touches
📝 Generate docstrings
  • Commit to this branch
  • Create a new PR
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR
  • Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.

@CodeMeAPixel
CodeMeAPixel merged commit ff2e203 into production Oct 4, 2026
8 checks passed
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