Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Chore] Update yarn to v4.6.0 #11874

Open
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

Philzen
Copy link
Contributor

@Philzen Philzen commented Jan 2, 2025

This updates the whole stack (incl. create-redwood-app) to the latest version of Yarn.

@Philzen Philzen force-pushed the chore/update-yarn-to-latest branch from d11427e to 516e469 Compare January 2, 2025 15:55
@Philzen Philzen force-pushed the chore/update-yarn-to-latest branch from 516e469 to 1ddb2fa Compare January 2, 2025 16:14
@Philzen Philzen marked this pull request as ready for review January 2, 2025 22:18
@Tobbe Tobbe added the release:chore This PR is a chore (means nothing for users) label Jan 6, 2025
@Tobbe Tobbe added this to the next-release-patch milestone Jan 6, 2025
@Tobbe
Copy link
Member

Tobbe commented Jan 6, 2025

@Philzen Can you please update the PR description?
And just to double check, these changes should not have any affect on existing RW projects, right?

Or, well, I guess, technically if someone was doing yarn create redwood-app in their own CI things would change because it would now be yarn 4.6 instead of 4.4. But no one does that? Right? 😰 😀

@Philzen
Copy link
Contributor Author

Philzen commented Jan 6, 2025

@Philzen Can you please update the PR description?

Done.

And just to double check, these changes should not have any affect on existing RW projects, right?

I wouldn't think so – as one can see from the yarn.lock diffs, the resolutions are identical, only a newer hash for the Typescript version, which won't have an effect on RW projects consuming the compiled npm package.

Actually, i was intending this for the next minor or major version... otherwise, technically, the upgrade guide would need to be amended to suggest upgrading to yarn 4.6 i guess ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release:chore This PR is a chore (means nothing for users)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants