Repository navigation
Package Engine retirement and search fixes in Server 1.6.558 - #393
Merged
Merged
Conversation
chen21019
deleted the
verification/server558-managed-retirement-search
branch
October 29, 2026 19:36
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.
Package the original qualified Engine 0.183.358 artifact to fix scoped service retirement and late-row typed resource searches. Web Console 1.6.199, bridge 0.2.1, other components, ordinary Full access and the existing vulnerability exception policy are unchanged.
Engine CI and required CodeQL passed: 374 suites / 3,631 tests, zero failures/errors, one existing conditional skip. Its 11 public assets were independently downloaded and hashed. Server packaging contract 47 cases and release-note format 4 cases passed.
Publication/startup/restart and fresh 8080 lifecycle plus real weak-model acceptance remain required. The 557 failure is retained; this batch does not include Catalog/Archive or claim complete frontend coverage. Install examples stay on the published 557 until the new immutable image is verified.