Update registry entries to version 6#19
Conversation
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (11)
✨ 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 |
0d2dd9f to
d74092c
Compare
d74092c to
aef3dae
Compare

Motivation
Settings and strategy registry entries need to move to the version 6 schema. In that schema, orderbook naming is replaced with raindex naming, including plural
raindexesblocks. The raindex local DB remote should also point at the current timestamped manifest, and the registry index should reference the updated content commit.Solution
settings.yamland strategy.rainfiles fromversion: 5toversion: 6.orderbooks:blocks toraindexes:.orderbook:references toraindex:.raindexlocal DB remote manifest URL.registryraw GitHub URLs to use commitd74092cb90baceac1909e54870f02793b6d85856.Checks
git diff --checksettings.yamlandsrc/*.rain