{{ message }}
🔄 chore: update schema URL to gh-aw v0.78.2#7082
Merged
Merged
Conversation
Pin mcp-gateway-config.schema.json to release tag v0.78.2 instead of v0.77.5 for reproducible 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.77.5tov0.78.2.Files Changed
internal/config/rules/rules.go—SchemaURLconstant updated tov0.78.2internal/config/validation_schema_test.go— hardcoded schema URLs updated tov0.78.2Why
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.
Note
🔒 Integrity filter blocked 6 items
The following items were blocked because they don't meet the GitHub integrity level.
get_latest_release: has lower integrity than agent requires. The agent cannot read data with integrity below "unapproved".list_releases: has lower integrity than agent requires. The agent cannot read data with integrity below "unapproved".list_releases: has lower integrity than agent requires. The agent cannot read data with integrity below "unapproved".list_releases: has lower integrity than agent requires. The agent cannot read data with integrity below "unapproved".list_releases: has lower integrity than agent requires. The agent cannot read data with integrity below "unapproved".list_releases: has lower integrity than agent requires. The agent cannot read data with integrity below "unapproved".To allow these resources, lower
min-integrityin your GitHub frontmatter: