fix: Update Brewfile to Node 22 for environment consistency (Fixes #6292) #1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ronment - Change node@16 to node@22 in Brewfile - Remove deprecated Homebrew taps (homebrew/core, homebrew/bundle, homebrew/services, homebrew/cask) - Align Brewfile with .tool-versions (22.13.0), CI config (Node 22), and development Dockerfile - Node 22.x is in Active LTS stage with full security support - Note: Dockerfile.production still uses Node 20 (separate issue for follow-up)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
The Brewfile specified node@20, but this conflicts with the project's actual configuration:
This creates version mismatches for macOS developers using Homebrew.
Solution
Update Brewfile to node@22 to maintain consistency across all environment configurations.
Changes Made
Why Node 22?
Related Issues
Testing