Skip to content

fix: use ST0x registry fallback in prod#119

Open
findolor wants to merge 1 commit into
mainfrom
fix/prod-st0x-registry-fallback
Open

fix: use ST0x registry fallback in prod#119
findolor wants to merge 1 commit into
mainfrom
fix/prod-st0x-registry-fallback

Conversation

@findolor
Copy link
Copy Markdown
Collaborator

@findolor findolor commented May 26, 2026

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

  • nix develop -c cargo fmt
  • nix develop -c rainix-rs-static

View with Codesmith Autofix with Codesmith
Need help on this PR? Tag @codesmith with what you need. Autofix is disabled.

Summary by CodeRabbit

  • Chores
    • Updated registry configuration to reference a new endpoint with pinned commit hash for improved version control and consistency.

Review Change Stack

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 26, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 54f6ed47-1f04-4737-9571-ab957d1445ed

📥 Commits

Reviewing files that changed from the base of the PR and between ebb328b and 7d9c356.

📒 Files selected for processing (1)
  • config/prod.toml

📝 Walkthrough

Walkthrough

The production configuration registry URL is updated to point to the ST0x-Technology/st0x.registry repository, pinned to a specific commit hash for reproducible builds.

Changes

Registry Configuration Update

Layer / File(s) Summary
Registry URL configuration
config/prod.toml
Production registry URL is changed to reference ST0x-Technology/st0x.registry at a pinned commit hash.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A registry renewed with a commit so fine,
Pinned tight to ensure the deployments align,
The rabbit declares with a hop and a cheer,
That stability comes when the versions are clear! 🐰

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: updating the production registry URL to use the ST0x registry fallback, which directly addresses the PR's core objective.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/prod-st0x-registry-fallback

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.

@blacksmith-sh
Copy link
Copy Markdown

blacksmith-sh Bot commented May 26, 2026

Blacksmith runners detected OOM events on the following jobs:

Job Details
rust test 3 of 4 View Job

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