Skip to content

ci: bump RAINIX_SHA to a3ce076 (rainix-static via fetchCargoVendor) - #370

Merged
thedavidmeister merged 1 commit into
mainfrom
2026-09-09-bump-sha-static-cdn
Sep 9, 2026
Merged

ci: bump RAINIX_SHA to a3ce076 (rainix-static via fetchCargoVendor)#370
thedavidmeister merged 1 commit into
mainfrom
2026-09-09-bump-sha-static-cdn

Conversation

@thedavidmeister

@thedavidmeister thedavidmeister commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

Bumps the pinned RAINIX_SHA in all 13 reusable workflows from dbcd9d3 to a3ce076, the merge of #369, so consumers resolve the rust-shell whose rainix-static is vendored through fetchCargoVendor from the static.crates.io CDN.

Without this, #369 is inert for consumers: at dbcd9d3 the shell still vendors rainix-static's crates through importCargoLock, which fetches from the crates.io API endpoint that 403s nix's User-Agent. Linux runs hit Cachix and never fetch; macOS runs miss the cache and fail before cargo test starts. rainlanguage/rain.math.float.deploy#24 is red on rs-test (macos-latest) twice in a row with cannot download crate-zip-2.4.2.tar.gz from any mirror under rainix-static-0.1.0.drv.

QA

  • Discriminating tests: n/a, a pin bump; verified against rain.math.float.deploy#24's macOS rs-test lane, which fails at dbcd9d3 on the fetch and should pass once consumers resolve a3ce076.
  • Mutations applied: n/a, one literal repeated across 13 files; the partial-bump failure mode is guarded by grep -rh 'RAINIX_SHA: ' .github/workflows/ | sort -u returning exactly one line, which it does.
  • Oracle: git rev-parse origin/main = a3ce07667219a5d86ddb2175fdae871402b39a2b, and the prior bump commits (ci: bump RAINIX_SHA to dbcd9d3 (rustfmt virtual workspace root) #364 and its predecessors) setting the same key in the same 13 files.
  • Category check: Refs Vendor rainix-static through fetchCargoVendor: crates.io/api now 403s nix #369, which changed the vendoring; this is the half that makes it reach consumers. Nothing else in scope.

🤖 Generated with Claude Code

https://claude.ai/code/session_01QyCCzi9WZPhuXcU1hwr2bq

Summary by CodeRabbit

  • Chores
    • Updated the pinned Rainix tooling revision used across automated build, test, verification, artifact, and release workflows.
    • Keeps CI and release processes aligned with the newer shared development environment.

@coderabbitai

coderabbitai Bot commented Sep 9, 2026

Copy link
Copy Markdown

Review Change StackReview Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: 52bcd45b-5ce3-43b4-9ffe-7e355d123e7d

📥 Commits

Reviewing files that changed from the base of the PR and between a3ce076 and ed35688.

📒 Files selected for processing (13)
  • .github/workflows/rainix-autopublish.yaml
  • .github/workflows/rainix-copy-artifacts.yaml
  • .github/workflows/rainix-manual-sol-artifacts.yaml
  • .github/workflows/rainix-manual-sol-verify.yaml
  • .github/workflows/rainix-rs-static.yaml
  • .github/workflows/rainix-rs-test.yaml
  • .github/workflows/rainix-rs-wasm-test.yaml
  • .github/workflows/rainix-rs-wasm.yaml
  • .github/workflows/rainix-sol-legal.yaml
  • .github/workflows/rainix-sol-static.yaml
  • .github/workflows/rainix-sol-test.yaml
  • .github/workflows/rainix-subgraph-test.yaml
  • .github/workflows/rainix-tag-release.yaml

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.


📝 Walkthrough

Walkthrough

The pull request updates RAINIX_SHA from the previous Rainix revision to a3ce07667219a5d86ddb2175fdae871402b39a2b across 13 GitHub workflow files.

Changes

Rainix workflow pin update

Layer / File(s) Summary
Update workflow Rainix pins
.github/workflows/rainix-*.yaml
All listed workflows use the newer Rainix revision for Nix development, testing, static analysis, artifact, legal, publishing, and release commands.

Priority: ➖ Normal

Estimated code review effort: 1 (Trivial) | ~5 minutes

Merge Risk: ⚪ Minimal · up to ed356

This updates CI workflows to use the newer pinned Rainix revision, intended to avoid Rust dependency download failures on macOS. The workflows retain immutable commit pins and present no remaining merge-readiness risk.

Possibly related PRs

  • rainlanguage/rainix#347: Updates the RAINIX_SHA pin across the same workflow files to a different Rainix revision.
🚥 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 clearly describes the main change: updating RAINIX_SHA to a3ce076 and identifying the rainix-static fetchCargoVendor change.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
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.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch 2026-09-09-bump-sha-static-cdn

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.

@thedavidmeister
thedavidmeister merged commit e51d1c7 into main Sep 9, 2026
17 checks passed
@github-actions

github-actions Bot commented Sep 9, 2026

Copy link
Copy Markdown

@coderabbitai assess this PR size classification for the totality of the PR with the following criterias and report it in your comment:

S/M/L PR Classification Guidelines:

This guide helps classify merged pull requests by effort and complexity rather than just line count. The goal is to assess the difficulty and scope of changes after they have been completed.

Small (S)

Characteristics:

  • Simple bug fixes, typos, or minor refactoring
  • Single-purpose changes affecting 1-2 files
  • Documentation updates
  • Configuration tweaks
  • Changes that require minimal context to review

Review Effort: Would have taken 5-10 minutes

Examples:

  • Fix typo in variable name
  • Update README with new instructions
  • Adjust configuration values
  • Simple one-line bug fixes
  • Import statement cleanup

Medium (M)

Characteristics:

  • Feature additions or enhancements
  • Refactoring that touches multiple files but maintains existing behavior
  • Breaking changes with backward compatibility
  • Changes requiring some domain knowledge to review

Review Effort: Would have taken 15-30 minutes

Examples:

  • Add new feature or component
  • Refactor common utility functions
  • Update dependencies with minor breaking changes
  • Add new component with tests
  • Performance optimizations
  • More complex bug fixes

Large (L)

Characteristics:

  • Major feature implementations
  • Breaking changes or API redesigns
  • Complex refactoring across multiple modules
  • New architectural patterns or significant design changes
  • Changes requiring deep context and multiple review rounds

Review Effort: Would have taken 45+ minutes

Examples:

  • Complete new feature with frontend/backend changes
  • Protocol upgrades or breaking changes
  • Major architectural refactoring
  • Framework or technology upgrades

Additional Factors to Consider

When deciding between sizes, also consider:

  • Test coverage impact: More comprehensive test changes lean toward larger classification
  • Risk level: Changes to critical systems bump up a size category
  • Team familiarity: Novel patterns or technologies increase complexity

Notes:

  • the assessment must be for the totality of the PR, that means comparing the base branch to the last commit of the PR
  • the assessment output must be exactly one of: S, M or L (single-line comment) in format of: SIZE={S/M/L}
  • do not include any additional text, only the size classification
  • your assessment comment must not include tips or additional sections
  • do NOT tag me or anyone else on your comment

hardyjosh added a commit that referenced this pull request Sep 10, 2026
…e) (#373)

Consumers' fork suites resolve `ROBINHOOD_RPC_URL` through the
`rpc-preflight` binary at the pinned rainix revision, so #371's table
entry is inert until this bump. Same 13-file bump as #370.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HiqQdxokJ4edjAFyAkN9G3
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