✨ Publish provider schema.json to release bucket#7093
Merged
chris-rock merged 6 commits intomainfrom Apr 2, 2026
Merged
Conversation
Publish standalone schema.json and provider.json files alongside the existing .tar.xz archives during provider releases. This enables downstream consumers (MCP, Nexus) to fetch provider schemas directly without downloading and extracting platform-specific archives. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The schema file uploads don't depend on the per-package loop variable, so move them after the loop using matrix.provider and the version from config.go directly. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Keep all uploads together in the loop for consistency with the existing pattern. The loop runs once per matrix job anyway. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Copy schema and provider JSON files to the root dist/ directory in the bundler script so the publish step uses dist/ for all artifacts. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
![mondoo-code-review[bot]](https://avatars.githubusercontent.com/in/2834902?s=60&v=4){kind=small}
There was a problem hiding this comment.
Provider schema and metadata JSON files are now published alongside release bundles.
Additional findings (file/line not in diff):
- 🔵
scripts/provider_bundler.sh:172— The SHA256SUMS file only covers*.xzfiles and won't include the newly copied_schema.jsonand_provider.jsonfiles. If consumers verify downloads against these checksums, the schema/provider files can't be validated. Consider adding them to the checksum (e.g.,shasum -a 256 ${PROVIDER_NAME}_${PROVIDER_VERSION}_*.xz ${PROVIDER_NAME}_${PROVIDER_VERSION}_*.json > ...) or generating a separate checksum file for them.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
schema.jsonandprovider.jsonfiles to the GCS release bucket during provider releases.tar.xzarchives atproviders/<name>/<version>/schema.jsonTest plan
schema.jsonandprovider.jsonto the versioned bucket pathhttps://releases.mondoo.com/providers/<name>/<version>/schema.json🤖 Generated with Claude Code