ci(release): publish the Artifact Hub repository metadata to the chart OCI repo - #276
Conversation
…t OCI repo Artifact Hub reads a repository's verified-publisher flag and ownership claim from a plain OCI artifact stored in the chart repository under the fixed `artifacthub.io` tag, identified by its layer media type. `helm push` cannot produce that shape, so the publish-helm job now pushes it with oras, straight from the file in Git. The metadata file lives at charts/artifacthub-repo.yml, outside the chart directory, so `helm package` does not bundle it into the chart tarball. oras joins cosign as a tool baked into the ci-image, for the same reason: publish-helm runs inside that image. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 31 seconds Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
✨ 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 |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Artifact Hub reads a chart repository's verified-publisher flag and ownership claim from a plain OCI artifact stored in that repository under the fixed
artifacthub.iotag, identified by its layer media type.helm pushcannot produce that shape, so thepublish-helmjob pushes it withoras, straight from the file in Git — re-pushed on every release, socharts/artifacthub-repo.ymlstays the source of truth.charts/artifacthub-repo.yml— the metadata file, in the upstream format, carrying therepositoryIDand the ownership-claimownersentry. It sits outsidecharts/gitops-reverser/on purpose, sohelm packagedoes not bundle it into the chart tarball..github/workflows/release.yml— a new step inpublish-helm, after the chart is pushed and signed. It gets its ownoras login: helm and cosign each write their own registry config, so neither login covers oras..devcontainer/Dockerfile—orasv1.3.3, checksum-verified, baked into the ci stage.publish-helmruns inside this image, the same reason cosign lives there.README.md— the Artifact Hub badge.docs/ci-overview.md— a row for the new artifact in the release-artifacts table.The badge and the Verified Publisher flag light up once the repository is registered in the Artifact Hub control panel and a release has run to push the
artifacthub.iotag.🤖 Generated with Claude Code