Skip to content

Comments

fix: remove set-public job from release workflow#497

Open
jpthor wants to merge 1 commit intomainfrom
fix/remove-set-public-job
Open

fix: remove set-public job from release workflow#497
jpthor wants to merge 1 commit intomainfrom
fix/remove-set-public-job

Conversation

@jpthor
Copy link
Contributor

@jpthor jpthor commented Jan 16, 2026

Summary

  • Remove set-public job from release workflow - GitHub's REST API does not support changing package visibility
  • Add comment explaining that visibility must be set manually via GitHub web UI

Background

The set-public job was failing with 404 errors because GitHub's REST API does not provide an endpoint to change container package visibility. This is a known limitation - visibility changes must be done through the GitHub web UI.

Manual step required

After first release, set package visibility to public via:
https://github.com/orgs/vultisig/packages → Package Settings → Change visibility to Public

Summary by CodeRabbit

  • Chores
    • Updated release workflow to require manual package visibility configuration via the GitHub UI instead of automated setup.

✏️ Tip: You can customize this high-level summary in your review settings.

…anges

GitHub's REST API does not support changing package visibility.
This must be done manually via the GitHub web UI.
Added comment with instructions for manual visibility change.
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jan 16, 2026

Walkthrough

Removed the set-public GitHub Actions job that automatically updated GHCR package visibility via REST API for verifier, worker, and tx_indexer containers. Replaced with comments documenting the need for manual visibility configuration through GitHub UI.

Changes

Cohort / File(s) Summary
GitHub Actions workflow
\.github/workflows/release.yaml``
Removed automated GHCR package visibility job (set-public) that performed PATCH calls for three container images. Added comments indicating manual GitHub UI configuration is required, as REST API does not support automatic visibility updates.
🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The pull request title accurately describes the main change: removing the set-public job from the release workflow as documented in the changeset.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch fix/remove-set-public-job

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@RaghavSood RaghavSood requested a review from webpiratt January 20, 2026 08:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant