fix(deploy): prepare bounded production deployment and patch dependencies - #62
Merged
Merged
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
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.
Production deploys can target a configured restricted SSH account, enforce one CPU and 512 MB per website instance, and verify the private host ingress independently from the public DNS destination. The existing workflow still verifies public HTTPS after the route switch.
Updates Next.js to 16.3.3 and vulnerable transitive packages; removes the obsolete rootParams experimental flag because the API is now stable. Cache Components and the existing root-parameter imports remain enabled.
Validation: local formatting, TypeScript and optimized build passed. Shell syntax passed on Linux. Full dependency audit is clean. The standalone readiness suite needs Linux CI because Windows denied its temporary symlink creation.