Document public packaging installation channels - #1038
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
🚧 Files skipped from review as they are similar to previous changes (2)
📝 WalkthroughWalkthroughRelease packaging dispatches now target ChangesPackaging distribution alignment
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
.github/workflows/release.yml (1)
1458-1464: 🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick winUpdate the dispatch token contract for
mesh-packaging.MESH_AGENT_IMAGES_DISPATCH_TOKENandRELEASE.mdstill describe access toMesh-LLM/mesh-agent-images, but this workflow now dispatches toMesh-LLM/mesh-packaging. Re-scope the token or rename/update the secret and docs so the dispatch can succeed.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.github/workflows/release.yml around lines 1458 - 1464, Update the cross-repository dispatch contract in the release workflow so the token configuration, validation message, and related RELEASE.md documentation consistently target Mesh-LLM/mesh-packaging instead of Mesh-LLM/mesh-agent-images. Preserve the existing GH_TOKEN usage and dispatch behavior while renaming or re-scoping the secret as needed.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@website/src/docs/pages/installing-linux.md`:
- Around line 25-30: Add concise Ubuntu and Arch command examples to the
native-package section, covering release-asset selection/download, fetching the
matching .sha256 sidecar, verifying with sha256sum --check, and installing the
local .deb or .pkg.tar.zst via apt install or pacman -U. Use placeholders or
clearly indicate that users must substitute the asset URL matching their distro,
architecture, and backend suffix, while preserving the existing release-assets
workflow.
---
Outside diff comments:
In @.github/workflows/release.yml:
- Around line 1458-1464: Update the cross-repository dispatch contract in the
release workflow so the token configuration, validation message, and related
RELEASE.md documentation consistently target Mesh-LLM/mesh-packaging instead of
Mesh-LLM/mesh-agent-images. Preserve the existing GH_TOKEN usage and dispatch
behavior while renaming or re-scoping the secret as needed.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 74c7137e-c1e5-4bf0-8a32-cc014f26127d
📒 Files selected for processing (6)
.github/workflows/release.ymlREADME.mdwebsite/src/_includes/components/cta-terminal.njkwebsite/src/docs/pages/installing-linux.mdwebsite/src/docs/pages/installing-macos.mdwebsite/src/docs/pages/installing-mesh.md
💤 Files with no reviewable changes (1)
- website/src/_includes/components/cta-terminal.njk
|
Addressed CodeRabbit’s outside-diff dispatch-contract finding in 6c2853f. RELEASE.md and the workflow diagnostic now target Mesh-LLM/mesh-packaging. The legacy MESH_AGENT_IMAGES_DISPATCH_TOKEN lookup name is intentionally retained for existing organization-secret compatibility, but its documented and enforced scope is Contents write on Mesh-LLM/mesh-packaging; GH_TOKEN, payload, and dispatch behavior are unchanged. |
1 participant
Closes #971.
Published availability validated for v0.73.1:
Local validation:
Summary by CodeRabbit
.deband Arch.pkg.tar.zstdownloads with SHA256 verification, plus OCI image usage and tag details.