Skip to content

chore: publish v1 VST packs — real sha256/bytes in vst_packs.json - #56

Merged
byrongamatos merged 1 commit into
mainfrom
chore/vst-packs-v1-manifest
Jul 22, 2026
Merged

chore: publish v1 VST packs — real sha256/bytes in vst_packs.json#56
byrongamatos merged 1 commit into
mainfrom
chore/vst-packs-v1-manifest

Conversation

@byrongamatos

Copy link
Copy Markdown
Contributor

Fills the 0-byte placeholders in data/vst_packs.json with the real sha256/bytes for the three per-platform VST packs, now published as immutable releases on got-feedback/feedback:

platform release bytes
mac vst-mac-v1 252,316,382
win vst-win-v1 244,558,568
linux vst-linux-v1 170,531,592

Packs were sliced from the fat vst/ tree by feedBack#1025's content_packs.py --vst (reproducible, per-platform: keeps one platform's binaries + shared bundle files, drops the other two + src/).

Effect: rb_vst_pack_status has_pack flips true, so the first-run prompt can fetch + sha256-verify the pack. This is the prerequisite for feedBack-desktop#124 to strip the bundled VSTs safely.

Verified end-to-end: downloaded vst-linux-pack-v1.zip from its release URL → 170531592 bytes, sha256 78312f13435fd760aa97a21161584f622330b1e42782267f7f869c944aa72dec, matching this manifest.

🤖 Generated with Claude Code

The three per-platform packs are now published as immutable releases on
got-feedback/feedback (vst-{mac,win,linux}-v1), sliced from the fat .vst3
tree by feedBack#1025's content_packs.py --vst. Replaces the 0-byte
placeholders so rb_vst_pack_status.has_pack flips true and the first-run
download prompt can actually fetch + sha256-verify the pack.

Verified end-to-end: downloading vst-linux-pack-v1.zip from its release URL
yields 170531592 bytes / sha256 78312f13… matching this manifest.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Signed-off-by: byrongamatos <xasiklas@gmail.com>
@coderabbitai

coderabbitai Bot commented Jul 22, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@byrongamatos, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 3 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: cee12051-62d2-4a7e-b4ea-a823cf985805

📥 Commits

Reviewing files that changed from the base of the PR and between 34c0682 and 5846391.

📒 Files selected for processing (1)
  • data/vst_packs.json
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/vst-packs-v1-manifest

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.

@byrongamatos
byrongamatos merged commit 8126051 into main Jul 22, 2026
1 check passed
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