Repository navigation
Release 0.22.1 - #381
Merged
Merged
Release 0.22.1#381
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.
This release is R011 for TypeScript (#377). With it, both rules from #89's table are done. The
pingdispatch signal now needs another MCP method in the same construct, rather than MCP anywhere in the file. That fixes the table's own repro: an SDK import beside a health check was abreakingfinding.Against 0.22.0, on the seven TypeScript repos I've been measuring against:
pingchecks in supergateway that sit outside any dispatch construct.pingentries in method tables.Checks:
validate_registry.py: 23 entries, 0 problems.