Merged
Conversation
Update the GitHub Actions workflow to bump the version in package.json after installing dependencies, ensuring that the version is not overwritten by pnpm install. This change enhances the reliability of version synchronization for both MCP and CLI repositories.
Enhance the GitHub Actions workflow by adding a workflow_dispatch trigger, allowing manual execution of the version synchronization process. This provides greater flexibility in managing version updates for MCP and CLI repositories.
…LI repositories Modify the GitHub Actions workflow to clone the MCP and CLI repositories into temporary directories instead of the current directory. This change improves the organization of the workflow and ensures that the latest OpenAPI specification is correctly referenced during the synchronization process.
Update the version retrieval command in the GitHub Actions workflow to strip the 'v' prefix from the version number in package.json. This change ensures that the version format is consistent for downstream processes.
style: Fix typo in custom entrypoint description
Adds a new /dashboard/home landing with welcome header, KPI cards (deploys/24h, build, CPU, memory) and a recent deployments list. Home is now the post-login landing and the destination for permission fallback redirects across the app. Projects remains accessible from the sidebar.
- Home: 4 KPI cards (projects, services, deploys/7d, status list), server column with icon in recent deployments, empty state with icon, dashboard card frame to match other pages. - Include libsql in project services count sort. - Fix bulk actions in environment page: libsql was missing from start, stop, move, delete and deploy handlers.
- Replace individual project and server queries with a consolidated homeStats query to streamline data retrieval for the dashboard. - Update the ShowHome component to utilize homeStats for displaying project, environment, application, and service counts, along with their status breakdown. - Enhance data handling for user permissions to ensure accurate statistics based on user access levels.
- Adjusted the Card component to have a minimum height of 85vh for better visual consistency. - Ensured the inner div has a full height to enhance the layout structure.
feat: add dashboard home page
…postgres 100-arg limit Closes #4256
…oo-many-args fix: preview deployments broken on v0.29.0 — postgres 100-arg limit
dosubot
bot
added
the
size:L
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
Comment on lines
+101
to
+107
| const { data: deployments } = api.deployment.allCentralized.useQuery( | ||
| undefined, | ||
| { | ||
| enabled: canReadDeployments, | ||
| refetchInterval: 10000, | ||
| }, | ||
| ); |
Contributor
There was a problem hiding this comment.
allCentralized.useQuery() fetches the complete deployment history, sorts it in JavaScript, and then discards all but 10 rows. On a busy instance this could transfer a large payload on every 10-second refresh just to display a 10-row list. Consider adding a server-side limit/offset or a dedicated recentDeployments query that returns only the N most-recent records.
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
3 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.
This PR promotes changes from
canarytomainfor version v0.29.1.🔍 Changes Include:
✅ Pre-merge Checklist:
Greptile Summary
This release (v0.29.1) bundles two main additions: a new dashboard home page showing aggregated service stats and recent deployments, and a targeted bug fix limiting the columns selected in
findPreviewDeploymentByIdto prevent exceeding PostgreSQL's 100-parameter limit during preview deployment operations.Confidence Score: 5/5
Safe to merge; all findings are P2 style suggestions with no blocking correctness issues.
The PostgreSQL parameter-limit bug fix is well-scoped and correct. The new homeStats and search queries correctly enforce member access control. Remaining feedback is stylistic and does not affect correctness or security.
No files require special attention beyond the P2 notes on project.ts and show-home.tsx.
Comments Outside Diff (1)
apps/dokploy/server/api/routers/project.ts, line 648-654 (link)projects.description ?? ""is always the Drizzle column reference at runtime — the column object is nevernullorundefinedin JavaScript — so the fallback""is dead code. If the intent is to treat SQL NULL descriptions as non-matching, theilikecomparison already does that (NULL ILIKE pattern → NULL, not TRUE). The?? ""can be removed for clarity.Reviews (1): Last reviewed commit: "chore: bump version to v0.29.1 in packag..." | Re-trigger Greptile