🚀 Release v0.26.2 #3254
Merged
🚀 Release v0.26.2 #3254
Conversation
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
fix(backups): optional chaining for logCleanupCron
…bopack script from package.json - Updated Next.js version in both root and dokploy package.json files to 16.0.10 for improved performance and features. - Removed the turbopack development script from the dokploy package.json to streamline the development process. - Added volumeBackup property to notification handling in multiple files for enhanced backup options.
…notifications-on-new-custom-webhook-notifications chore(dependencies): update Next.js to version 16.0.10 and remove tur…
- Updated the logic to disallow renaming the default environment while still allowing updates to its description and other properties. - Adjusted error message for clarity when attempting to rename the default environment.
- Added logic to disallow deletion of the default environment, throwing a BAD_REQUEST error if an attempt is made to delete it.
…ironment-variables fix(environment): prevent renaming of the default environment
- Updated the description for the environment file creation option to specify that the .env file will be created in the same directory as the Dockerfile during the build process, enhancing user understanding.
…ockerfile-directory fix(environment): clarify .env file creation instructions
… Registry - Updated validation schema to require that both Build Server and Build Registry must be selected together or both set to None. - Added informational alert to guide users on the selection requirements. - Enhanced onChange handlers to reset the corresponding field when one is set to "none".
…tion environment - Modified the project environment link to reference the default production environment instead of the first environment in the list, improving accuracy in navigation.
fix(build-server): enforce selection rules for Build Server and Build…
- Added a new `cleanupAllBackground` function to execute Docker cleanup commands in the background, allowing for immediate return and avoiding gateway timeouts. - Refactored existing cleanup functions to utilize a centralized `cleanupCommands` object for better maintainability and readability.
Fix/long request on cleanup
- Updated deployment logic across multiple API routes to run deployments in the background, allowing for immediate response and avoiding potential webhook timeouts. - Added error handling to log any failures during background deployment.
…-return-a-200-ok-causing-being-repeated-over-and-over refactor(deploy): execute deployments in background to prevent timeouts
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.26.2.🔍 Changes Include:
✅ Pre-merge Checklist: