Merged
Conversation
Update MCP Gateway JSON schema validation URL from v0.53.2 to v0.53.4 for reproducible, deterministic configuration validation. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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
1 participant
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.
Schema URL Update
Updates the MCP Gateway JSON schema validation URL from
v0.53.2tov0.53.4.Files Changed
internal/config/validation_schema.go—schemaURLvariable updated tov0.53.4internal/config/rules/rules.go—SchemaURLconstant updated tov0.53.4internal/config/validation_schema_test.go— hardcoded schema URLs updated tov0.53.4Why
Pinning to a specific release tag ensures reproducible, deterministic configuration validation — the schema won't silently change between runs.
Release Notes
See the gh-aw release notes for changes in this schema version.
Warning
The following domain was blocked by the firewall during workflow execution:
invalidhostthatdoesnotexist12345.comTo allow these domains, add them to the
network.allowedlist in your workflow frontmatter:See Network Configuration for more information.