Repository navigation
Package Web203 and Engine363 for Server v1.6.562 - #404
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.
Packages published Web Console 1.6.203 / optional bridge 0.2.5 and Engine v0.183.363 using their original qualified artifact hashes and producer commits. This includes the pending-review footer layout fix, restricted API-key discovery and safe confirmation errors, correct External Service before-values, retained ServiceIndex cleanup authorization, and official MariaDB JDBC 3.5.11.
Catalog/Compose and other component pins, VEX statements, vendor decisions, opt-in defaults and installation examples remain unchanged. The local component-input comment now refers to the actual required asset set.
Validation: all 12 Engine and 13 Web public assets passed anonymous byte/hash verification; 47 focused packaging contract tests and diff checks pass. Server publisher gates and matching 8080 runtime acceptance remain required; this PR does not claim full WebMCP feature completion.