Repository navigation
Per-network dApp deployments and spotlight refresh - #10
Conversation
…ngs. Introduce mainnet/testnet deployment URLs so Hub can open the right live entry, spotlight WinSaf and Safhandle, add Dyma on testnet, and remove Leap, Cosmostation, safrochain.com, Brand Assets, and Gaming & Missions. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Warning Review limit reached
Next review available in: 56 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. 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 (2)
📝 WalkthroughWalkthroughThe change adds optional per-network deployment metadata to the manifest schema, validation, documentation, application manifests, and registry records. It also adds Dyma and WinSaf, updates Safhandle, refreshes featured entries, and removes obsolete application manifests. ChangesPer-network deployment metadata
Estimated code review effort: 4 (Complex) | ~45 minutes Sequence Diagram(s)sequenceDiagram
participant ManifestConsumer
participant app.manifest.schema.json
participant validate.mjs
participant registry.json
ManifestConsumer->>app.manifest.schema.json: Validate deployment structure
ManifestConsumer->>validate.mjs: Validate live deployment URLs
validate.mjs-->>ManifestConsumer: Return validation result
ManifestConsumer->>registry.json: Read network deployment metadata
registry.json-->>ManifestConsumer: Return app records and deployment URLs
Possibly related PRs
Suggested labels: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches 💡 1⚔️ Resolve merge conflicts 💡
📝 Generate docstrings
🧪 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 |
Keep Dyma listing copy from main, mark testnet live with landing URL, and keep WinSaf live on mainnet and testnet with spotlight deployments. Co-authored-by: Cursor <cursoragent@cursor.com>
![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
🤖 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 `@registry.json`:
- Around line 847-892: Regenerate the WinSaf entry in registry.json from
apps/winsaf/json/app.json using the repository’s registry builder. Ensure the
generated entry includes both declared mainnet and testnet deployments, the
deployments field, and updated status metadata instead of the stale testnet-only
values; commit the builder’s output without manually diverging from the source
manifest.
🪄 Autofix
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: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 92e6015d-bb85-44d4-9f1b-36481c43aee4
⛔ Files ignored due to path filters (7)
apps/brandassets/img/logo.pngis excluded by!**/*.pngapps/cosmostation/img/logo.pngis excluded by!**/*.pngapps/dyma/img/logo.pngis excluded by!**/*.pngapps/gamingplaceholder/img/logo.pngis excluded by!**/*.pngapps/leap/img/logo.pngis excluded by!**/*.pngapps/safrochaincom/img/logo.pngis excluded by!**/*.pngapps/winsaf/img/logo.pngis excluded by!**/*.png
📒 Files selected for processing (33)
README.mdapps/brandassets/json/app.jsonapps/cosmostation/json/app.jsonapps/docssafrochain/json/app.jsonapps/dyma/json/app.jsonapps/eightsaf/json/app.jsonapps/ekival/json/app.jsonapps/explorertestnet/json/app.jsonapps/faucettestnet/json/app.jsonapps/gamingplaceholder/json/app.jsonapps/githuborg/json/app.jsonapps/grantprogram/json/app.jsonapps/ibcbridge/json/app.jsonapps/keplr/json/app.jsonapps/leap/json/app.jsonapps/mintscan/json/app.jsonapps/momotrack/json/app.jsonapps/osmosisibc/json/app.jsonapps/pesaex/json/app.jsonapps/safhandle/json/app.jsonapps/safrimba/json/app.jsonapps/safrochaincom/json/app.jsonapps/safrohub/json/app.jsonapps/safroidvision/json/app.jsonapps/sgov/json/app.jsonapps/smultisig/json/app.jsonapps/valopersmainnet/json/app.jsonapps/valoperstestnet/json/app.jsonapps/winsaf/json/app.jsonfeatured.jsonregistry.jsonschemas/app.manifest.schema.jsonscripts/validate.mjs
💤 Files with no reviewable changes (5)
- apps/safrochaincom/json/app.json
- apps/brandassets/json/app.json
- apps/cosmostation/json/app.json
- apps/leap/json/app.json
- apps/gamingplaceholder/json/app.json
There was a problem hiding this comment.
Caution
Inline review comments failed to post. This is likely due to GitHub's internal server error or limits when posting large numbers of comments. If you are seeing this consistently it is likely a permissions issue. Please check "Moderation" -> "Code review limits" under your organization settings.
Actionable comments posted: 1
🤖 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 `@registry.json`:
- Around line 847-892: Regenerate the WinSaf entry in registry.json from
apps/winsaf/json/app.json using the repository’s registry builder. Ensure the
generated entry includes both declared mainnet and testnet deployments, the
deployments field, and updated status metadata instead of the stale testnet-only
values; commit the builder’s output without manually diverging from the source
manifest.
🪄 Autofix
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: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 92e6015d-bb85-44d4-9f1b-36481c43aee4
⛔ Files ignored due to path filters (7)
apps/brandassets/img/logo.pngis excluded by!**/*.pngapps/cosmostation/img/logo.pngis excluded by!**/*.pngapps/dyma/img/logo.pngis excluded by!**/*.pngapps/gamingplaceholder/img/logo.pngis excluded by!**/*.pngapps/leap/img/logo.pngis excluded by!**/*.pngapps/safrochaincom/img/logo.pngis excluded by!**/*.pngapps/winsaf/img/logo.pngis excluded by!**/*.png
📒 Files selected for processing (33)
README.mdapps/brandassets/json/app.jsonapps/cosmostation/json/app.jsonapps/docssafrochain/json/app.jsonapps/dyma/json/app.jsonapps/eightsaf/json/app.jsonapps/ekival/json/app.jsonapps/explorertestnet/json/app.jsonapps/faucettestnet/json/app.jsonapps/gamingplaceholder/json/app.jsonapps/githuborg/json/app.jsonapps/grantprogram/json/app.jsonapps/ibcbridge/json/app.jsonapps/keplr/json/app.jsonapps/leap/json/app.jsonapps/mintscan/json/app.jsonapps/momotrack/json/app.jsonapps/osmosisibc/json/app.jsonapps/pesaex/json/app.jsonapps/safhandle/json/app.jsonapps/safrimba/json/app.jsonapps/safrochaincom/json/app.jsonapps/safrohub/json/app.jsonapps/safroidvision/json/app.jsonapps/sgov/json/app.jsonapps/smultisig/json/app.jsonapps/valopersmainnet/json/app.jsonapps/valoperstestnet/json/app.jsonapps/winsaf/json/app.jsonfeatured.jsonregistry.jsonschemas/app.manifest.schema.jsonscripts/validate.mjs
💤 Files with no reviewable changes (5)
- apps/safrochaincom/json/app.json
- apps/brandassets/json/app.json
- apps/cosmostation/json/app.json
- apps/leap/json/app.json
- apps/gamingplaceholder/json/app.json
🛑 Comments failed to post (1)
registry.json (1)
847-892: 🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win
Regenerate the WinSaf registry entry.
apps/winsaf/json/app.jsondeclares live mainnet and testnet deployments. This registry entry still lists only testnet, omitsdeployments, and retains the old testnet-only status text. Consumers ofregistry.jsonwill receive incorrect network availability. Run the registry builder and commit its output.🤖 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 `@registry.json` around lines 847 - 892, Regenerate the WinSaf entry in registry.json from apps/winsaf/json/app.json using the repository’s registry builder. Ensure the generated entry includes both declared mainnet and testnet deployments, the deployments field, and updated status metadata instead of the stale testnet-only values; commit the builder’s output without manually diverging from the source manifest.
1 participant
Summary
deployments(mainnet/testnet live + URL) to the app manifest schema and registryTest plan
npm run validatepassesSummary by CodeRabbit
New Features
Updates