chore: bump pinned rainix to latest main#2579
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe ChangesPrettier Toolchain Removal
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 3❌ Failed checks (3 inconclusive)
✅ Passed checks (2 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 |
# Conflicts: # flake.lock # package-lock.json # package.json
Closes #2575.
What
Why now
The `rainix` pin was at `f3bdb28f` (2024-05-03) — about 2 years stale. Picks up:
The bumped rainix supplies prettier via its pre-commit hook bundle and adds a `no-consumer-prettier` hook that forbids prettier deps in consumer `package.json`. That's why the prettier cleanup is bundled in this same PR — bumping rainix without it would fail the new lint hook on every consumer.
Implementation notes
`nix flake update` wouldn't land on the latest rainix commit even with `--refresh` and `--option tarball-ttl 0` (nix 2.18.1 fetcher cache stickiness on `github:rainlanguage/rainix` HEAD lookups). `flake.lock` was hand-edited to set `rev` + `narHash` + `lastModified` for the rainix node after a full `nix flake update` to surface the new transitive inputs (notably `git-hooks-nix`).
🤖 Generated with Claude Code
Summary by CodeRabbit