feat: Update build dependencies to their latest versions #3290
Conversation
- pnpm: 9.12.0 → 10.26.0 - Docker: 28.5.2 → 29.1.3 - Nixpacks: 1.39.0 → 1.41.0 - Railpack: 0.2.2 → 0.15.1 - buildpacks/pack: 0.35.0 → 0.39.1
Update to latest stable versions: - pnpm: 9.12.0 → 10.26.0 - Docker: 28.5.0/28.5.2 → 29.1.3 - Nixpacks: 1.39.0 → 1.41.0 - Railpack: 0.2.2/0.15.0 → 0.15.1 - buildpacks/pack: 0.35.0 → 0.39.1 Files updated: - All Dockerfiles (main, schedule, cloud, server) - All package.json files (root, server, api, schedules, dokploy) - GitHub workflow (pull-request.yml) - Server setup script - Database schema and DBML files - Test fixtures - UI components
Siumauricio
left a comment
Siumauricio
left a comment
There was a problem hiding this comment.
Hello, I appreciate this PR, but updating to newer versions of Docker can cause problems. Versions of packages such as Docker or pnpm are managed by the dokploy team when deemed necessary, when there is a vulnerability, or when it is the right time to update. If you wish, you can remove those changes, and I can accept the update from nixpacks and railpack.
Updated pnpm version from 9.15.9 to 9.12.0 and Docker version from 29.1.3 to 28.5.2.
@Siumauricio Hi, thanks for the feedback. I have removed those changes as requested. The reasons I previously introduced those upgrades were:
|
| .default("idle"), | ||
| buildType: buildType("buildType").notNull().default("nixpacks"), | ||
| railpackVersion: text("railpackVersion").default("0.2.2"), | ||
| railpackVersion: text("railpackVersion").default("0.15.1"), |
There was a problem hiding this comment.
You need to generate a new migration
3 participants
What is this PR about?
This updates the build tools to their latest stable version.
Checklist
Before submitting this PR, please make sure that:
canarybranch.Issues related (if applicable)
Screenshots (if applicable)