🚀 Release v0.29.11#4767
Conversation
- Integrated a new Badge component to display an "Enterprise" label when a valid license is detected. - Enhanced the sidebar layout to accommodate the new badge alongside the organization name, improving user visibility of license status.
…rieval - Added a new service to fetch public whitelabeling configuration for unauthenticated contexts. - Updated the whitelabeling router to utilize the new service for public requests. - Enhanced license validation checks to ensure proper access control based on organization licenses.
- Wrapped the project name in a paragraph element to improve text styling and ensure proper truncation for better readability. - Enhanced the layout of the EnvironmentPage component for a more polished user interface.
…settings page - Eliminated the EnterpriseFeatureGate card for Application Authentication from the SSO settings page to streamline the UI. - This change simplifies the layout and focuses on relevant features for users, particularly in non-cloud environments.
fix(requests): chart not visible in Requests tab
…eleases feat(ci): attach install.sh to each GitHub release
feat(ci): pin install.sh release asset to the released version
fix(databases): resolve crash when opening rebuild database dialog
fix(ui): resolve CommandDialog crash on CMD/CTRL + J shortcut
fix(ui): enable vertical scroll on collapsed sidebar
|
Hey @Siumauricio I was following up on my recently merged PRs and noticed that this release failed. After analyzing the CI logs, I realized that my PR #4761 was the root cause, it introduced a minor formatting issue that failed the strict biome check. (Even though my other PR, #4755, was opened first, it was merged after #4761. Since #4761 broke the canary branch, all subsequent merges, including #4755, automatically failed because they inherited the broken state). There were no logical bugs, just the linter strictly preferring I have instantly opened a new PR #4768 to fix the formatting, and all the checks on it are already green! ✅ Since these were my very first PRs to the repository, the GitHub Actions (like the format checks and @autofix.ci) didn't run automatically for me before they were merged due to permissions. Otherwise, I would have caught and fixed this immediately! |
chore(ui): fix biome formatting issues from #4761
fix(sso): apply trusted origin changes without server restart
feat(scim): SCIM 2.0 user provisioning (enterprise)
The @dokploy/server modules get bundled multiple times per process (esbuild inline copy, compiled node_modules copy, and several Next.js chunks via transpilePackages), so every module-level side effect ran once per copy: up to 6 postgres pools, 6 dockerode clients and 6 better-auth instances in the server process, plus the repeated 'Using Docker socket' logs at boot. - db/index.ts: use the globalThis cache in production too (one pool per process) - constants/index.ts: cache the dockerode client on globalThis - lib/auth.ts: wrap betterAuth() in a factory and cache the instance - Dockerfile: exec node directly instead of leaving pnpm resident (~100MB RSS)
perf: share db, docker and auth singletons across duplicated bundles
feat: make concurrent builds an OSS feature
- Added @better-auth/scim version 1.6.23 to package.json. - Updated versions of several @codemirror packages in pnpm-lock.yaml: - @codemirror/autocomplete from 6.20.0 to 6.20.3 - @codemirror/language from 6.12.1 to 6.12.4 - @codemirror/search from 6.6.0 to 6.7.1 - @codemirror/view from 6.39.15 to 6.43.6
- Added a "Ports" column to display container port information with sorting functionality. - Implemented a dropdown menu item to copy the Container ID to the clipboard with a success toast notification. - Introduced a state filter dropdown to filter containers by their current state, with options for all defined states. - Added a refresh button to allow manual refreshing of the container list.
This PR promotes changes from
canarytomainfor version v0.29.11.🔍 Changes Include:
✅ Pre-merge Checklist: