Repository navigation
Package Engine 0.183.364 lifecycle fixes - #407
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.
Server v1.6.562 native acceptance exposed two lifecycle failures: removing a standalone container could deny its uniquely owned OS Image cleanup, and switching an External Service from hostname to IP targets could throw while retiring the old hostname unit.
Package published Engine v0.183.364 with the exact private cleanup authority and null-safe, exact hostname comparison. Retain Web Console 1.6.203, optional Bridge 0.2.5, all other component pins, configuration defaults and existing vulnerability decisions. README installation commands stay on published Server562 until this image is released.
Validation: original Engine CI passed 3,872 tests in 416 suites (14 new lifecycle cases; zero failure/error, one existing platform skip), required CodeQL passed, and all 12 public assets passed anonymous SHA256 readback. Local Server packaging contract: 47 PASS; release-note renderer: 4 PASS. VEX statements and vendor entries are unchanged; only release identities advance. The original Server publisher and matching QA deployment/business acceptance remain required. No production deployment or complete frontend PASS is claimed.