[Bl4ckBl1zZ]

What is this PR about?

This PR integrates Dokploy upstream canary through e0c8d80cd (2026-10-17). The fork last synced at 53464e909 in #42, so the range is 53464e909..e0c8d80cd: 12 commits across 4 upstream PRs.

Upstream changes:

• Route 53 (fix: decode Route53 octal escapes in record names Dokploy/dokploy#5553): record names containing octal escapes (for example \052 for * in wildcard records) are decoded correctly.
• Telegram notifications (fix: escape HTML and truncate long messages in Telegram notifications Dokploy/dokploy#5694): message fields are HTML-escaped and long error output is truncated, so notifications with <, & or long logs are no longer rejected by the Telegram API. sendTelegramNotification now throws when Telegram rejects a message, so a failing test notification shows an error instead of a false success. Deployment and backup senders already wrap each notification in try/catch, so a Telegram failure is logged and does not fail the deployment.
• Self-hosted Stripe guard (fix(billing): guard loadStripe behind key check for self-hosted instances Dokploy/dokploy#5693): the billing page and the onboarding plan step only call loadStripe when NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY is set, which avoids a client error on self-hosted installs.
• Service header overflow on mobile (fix(ui): prevent service header overflow on mobile Dokploy/dokploy#5590): long service names, app names and server badges truncate instead of overflowing on the eight service pages.

Integration review

I resolved 9 conflicts by hand:

• Service page headers (application, compose, postgres, mysql, mariadb, mongo, redis, libsql): kept the fork's responsive header, which stacks vertically on mobile (flex-col gap-3 sm:flex-row sm:justify-between sm:items-start), and added upstream's min-w-0/flex-1/truncate overflow fixes.
  • Upstream caps the server-badge column at max-w-[45%], which assumes the single-row layout. The fork stacks the header on mobile, so I apply the cap only from sm up and leave the column at max-w-full below that.
• Breadcrumb: kept the fork's shared BREADCRUMB_LABEL_CLASS and added upstream's new title tooltip on the project label.

Fork behavior checked:

• Removed license gating: no hasValidLicense, isEnterpriseCloud or licenseKey references outside tests. The billing page change is only the Stripe guard.
• pipeBetweenServers fix from chore(sync): integrate Dokploy canary through 53464e9 #42: still present in remoteStream.ts; this range doesn't touch it.
• Unchanged areas: Cloudflare, Tailscale, Halifax CI, the GHCR publish/release workflows, self-update and versioning are not touched. The app version stays 0.44.0.

No Product Overview changes are needed in CLAUDE.md; these are fixes only.

Migrations, dependencies, environment

• Migrations: none. Two migration:generate runs both reported "No schema changes".
• Dependencies: none changed. pnpm install --frozen-lockfile passes.
• Environment: no new variables. NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY is now optional on the client.
• OpenAPI: unchanged, since no routers changed.

Verification (local)

• pnpm install --frozen-lockfile: pass
• Migration generation twice: no changes, no drift
• pnpm run format-and-lint: pass (0 errors)
• Typecheck (pnpm run typecheck --checkers 2) for packages/server, apps/dokploy, apps/api and apps/schedules: pass
• Vitest: 1344 passed, 11 skipped, 4 failed. The 4 are application.real.test.ts REAL deployment tests. They need docker build / nixpacks build, and this machine has neither binary. These are infra-only failures, the same as in chore(sync): integrate Dokploy canary through 5df820a #38–chore(sync): integrate Dokploy canary through 53464e9 #42; the hosted test job runs them.
• Production build with an ephemeral BETTER_AUTH_SECRET (never printed or stored): pass

Hosted checks

On a3addbcea, pr-check (build), pr-check (test) and pr-check (typecheck) all pass on the first run. The hosted test job also runs the real Docker deployment tests that can't run locally.

Risk / rollout / rollback

Risk is low: small UI and notification fixes with no schema or dependency changes.

• Rollout: deploy as usual. If Telegram notifications are configured, send a test notification.
• Rollback: roll back the application image. There is no migration to reverse.

Checklist

• You created a dedicated branch based on the canary branch. (This branch is based on the fork's main and integrates upstream canary.)
• You have read the suggestions in the CONTRIBUTING.md file https://github.com/Dokploy/dokploy/blob/canary/CONTRIBUTING.md#pull-request
• You have tested this PR in your local instance. (Automated checks and a production build ran locally; no live Dokploy instance was changed.)

Issues related (if applicable)

Not applicable for this upstream integration PR.

🤖 Generated with Claude Code

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: 56ff469f-03aa-4003-a1c1-7138e677956b

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autofix · 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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}