Skip to content

chore: bump pinned rainix to latest main#2579

Open
thedavidmeister wants to merge 2 commits into
mainfrom
2026-05-20-bump-rainix
Open

chore: bump pinned rainix to latest main#2579
thedavidmeister wants to merge 2 commits into
mainfrom
2026-05-20-bump-rainix

Conversation

@thedavidmeister
Copy link
Copy Markdown
Contributor

@thedavidmeister thedavidmeister commented May 20, 2026

Closes #2575.

What

  • Pins `rainix` flake input at `d444279bc7` (latest `rainlanguage/rainix` main as of 2026-05-19).
  • Removes `prettier`, `prettier-plugin-svelte`, `prettier-plugin-tailwindcss` from root `package.json`; regenerates `package-lock.json` to drop the corresponding entries.

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

  • Chores
    • Removed development formatting toolchain dependencies.

Review Change Stack

@thedavidmeister thedavidmeister self-assigned this May 20, 2026
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 20, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 832ef5a2-2207-48c2-bc06-995175fb2f2a

📥 Commits

Reviewing files that changed from the base of the PR and between 5054ade and ca1ec61.

⛔ Files ignored due to path filters (2)
  • flake.lock is excluded by !**/*.lock
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (1)
  • package.json

📝 Walkthrough

Walkthrough

The devDependencies section of package.json is updated to remove the Prettier code formatter and its Svelte and Tailwind CSS plugins. All other project configuration and dependency declarations remain unchanged.

Changes

Prettier Toolchain Removal

Layer / File(s) Summary
Remove Prettier and plugins from devDependencies
package.json
The prettier, prettier-plugin-svelte, and prettier-plugin-tailwindcss packages are deleted from devDependencies; surrounding dependency entries are reordered or remain unchanged.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A world without semicolon rules to fight,
No plugin wars or formatting might,
The code flows free in its natural way,
Prettier's gone—let's code today!

🚥 Pre-merge checks | ✅ 2 | ❌ 3

❌ Failed checks (3 inconclusive)

Check name Status Explanation Resolution
Title check ❓ Inconclusive The PR title mentions bumping rainix, but the actual changes show package.json Prettier dependency removals with no visible flake.lock updates in the raw summary. Clarify whether flake.lock was updated as expected for the rainix bump, or if the title should reflect the Prettier removal focus.
Linked Issues check ❓ Inconclusive The PR removes Prettier deps as required by the new rainix's lint hook, but the raw summary lacks evidence of the primary flake.lock rainix update from f3bdb28f to d444279b. Verify that flake.lock was updated with the new rainix revision and related changes, as described in issue #2575.
Out of Scope Changes check ❓ Inconclusive Removing Prettier dependencies aligns with the PR objectives (required by new rainix's no-consumer-prettier hook), but the raw summary does not show flake.lock changes that were the primary scope of issue #2575. Confirm that all flake.lock changes related to the rainix bump are present in the PR, as the raw summary only documents package.json modifications.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ 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 2026-05-20-bump-rainix

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.

# Conflicts:
#	flake.lock
#	package-lock.json
#	package.json
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.

chore: bump pinned rainix to latest

1 participant