Repository navigation
Package typed WebMCP resource workflows in Server 1.6.556 - #386
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 the published Web Console 1.6.199 and Engine 0.183.356 original CI artifacts for typed metadata queries and human-reviewed basic Stack, Service and Container changes. Stack lifecycle preflights affected children and Global Services reject unsupported manual scale counts. Other component pins remain unchanged.
Component CI/required CodeQL passed; release assets passed anonymous hash and same-tree producer verification. Web archive provenance/SBOM attestations and all 124 archived files were verified. Server pin consistency passes. The standard Server source gates, CodeQL and publisher checks remain required. New 8080 lifecycle, UI and role/cross-ID acceptance follows publication; existing unaffected PASS is retained separately. Advanced forms, Catalog launch and other adapters remain pending, not full frontend coverage.
Updates current README examples, compatibility and AI activation/rollback documentation. No production deployment or runtime patch.