Skip to content

Conversation

@ericallam
Copy link
Member

No description provided.

@changeset-bot
Copy link

changeset-bot bot commented Jan 15, 2026

⚠️ No Changeset found

Latest commit: 0d514d2

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jan 15, 2026

Caution

Review failed

The pull request is closed.

Walkthrough

Updated image and Node.js version pins and documentation: apps/supervisor/.nvmrc changed Node.js from v22.22.0 to v22.12.0; apps/supervisor/Containerfile replaced the pinned base image digest and tag with node:22-alpine@sha256:...; docker/Dockerfile updated ARG NODE_IMAGE to node:20.20-bullseye-slim@sha256:.... Added a “Docker Image Guidelines” section and migration-related guidance (PostgreSQL index rules, migration steps, ClickHouse migration format) to CLAUDE.md. No exported/public API declarations were modified.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1
❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Description check ⚠️ Warning The pull request description is completely empty, missing all required sections from the template including Testing, Changelog, and Issue reference. Add a complete description following the repository template, including issue number, testing details, and a changelog entry explaining why the Node.js upgrades were reverted.
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately describes the main change: reverting Node.js version upgrades in supervisor configuration files.
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.



📜 Recent review details

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 65599c3 and 0d514d2.

📒 Files selected for processing (1)
  • CLAUDE.md

✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.


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.

@ericallam ericallam marked this pull request as ready for review January 15, 2026 11:46
@ericallam ericallam changed the title fix(supervisor): undo node.js upgrades as they are not necessary currently fix(repo): undo node.js supervisor upgrades and use the multiplatform node.js digest in Dockerfile Jan 15, 2026
Document the requirement to use multiplatform/index digests instead
of architecture-specific digests when updating Docker images.
@ericallam ericallam merged commit aa69b90 into main Jan 15, 2026
4 of 5 checks passed
@ericallam ericallam deleted the ea-branch-114 branch January 15, 2026 11:49
@vibe-kanban-cloud
Copy link

Review Complete

Your review story is ready!

View Story

Comment !reviewfast on this PR to re-generate the story.

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.

3 participants