fix: use ST0x registry fallback in prod#119
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe production configuration registry URL is updated to point to the ST0x-Technology/st0x.registry repository, pinned to a specific commit hash for reproducible builds. ChangesRegistry Configuration Update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
|
Blacksmith runners detected OOM events on the following jobs:
|
Motivation
Prod currently needs a fallback registry that can initialize the deployed raindex client when no private registry artifact is available. The previous fallback points at the public rain.strategies registry, which failed to initialize during recovery.
Solution
Update the prod fallback registry URL to the ST0x registry commit that was verified during recovery:
https://raw.githubusercontent.com/ST0x-Technology/st0x.registry/e1fa474d45f126d70cdf2d3acd893e15c836ef03/registry
Checks
Need help on this PR? Tag
@codesmithwith what you need. Autofix is disabled.Summary by CodeRabbit