Skip to content

Conversation

@grunch
Copy link
Member

@grunch grunch commented Nov 21, 2025

Summary by CodeRabbit

  • New Features

    • Added a server configuration entry to support an additional content distribution endpoint.
  • Updates

    • Switched from a wildcard APK selection to an explicit arm64-v8a build, improving device compatibility and installation reliability.

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

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Nov 21, 2025

Walkthrough

Adds a top-level blossom_servers key with a CDN URL to zapstore.yaml and replaces a wildcard APK asset entry with a single explicit APK filename entry; no control-flow or code changes.

Changes

Cohort / File(s) Summary
Manifest configuration
zapstore.yaml
Added blossom_servers top-level key containing https://cdn.zapstore.dev; replaced wildcard APK asset entry (- .*.apk) with an explicit APK filename entry (- mostro-vd+.d+.d+-arm64-v8a.apk).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

  • Areas to spot-check:
    • Confirm blossom_servers URL correctness and accessibility.
    • Verify the explicit APK pattern covers intended releases previously matched by the wildcard.

Possibly related PRs

  • Add zapstore spec file #302 — Modifies the same zapstore.yaml manifest and previously introduced the wildcard APK asset entry that this change narrows.

Poem

🐰 I hopped through YAML, neat and spry,

Added a CDN beneath the sky.
Wildcards trimmed to one tidy name,
APKs now find their rightful frame.
Happy hops — the manifest's tame! 🥕

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'Update zapstore.yaml file with split apk files' accurately describes the main changes: updating the zapstore.yaml configuration file and replacing a wildcard APK entry with an explicit split APK file entry.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch zapstore-split-assets

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4cb778e and 2b7ddc9.

📒 Files selected for processing (1)
  • zapstore.yaml (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • zapstore.yaml
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: build

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.

@grunch grunch merged commit b23de1f into main Nov 21, 2025
2 checks passed
@grunch grunch deleted the zapstore-split-assets branch November 21, 2025 15:16
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.

2 participants