Current CRA version #9484
-
Hello CRA maintainers and community, I wanted to confirm the correct current version and double check if its ok to upgrade. I see on the main repo page the current version that is released and tagged is However checking the latest changelog and npm repo for I just wanted to check and ensure this was correct as I have been following for the release of CRA v4 and have noticed that PRs that make up the v4 release have been making their way in master already? (as seen in this comment for PRs needed for v4 #9131 (comment)). So didn't want to make this upgrade incase the release on NPM includes breaking changes for v4 and could cause more issues if upgrading. Can you help confirm and assist in my confusion? Thanks |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 4 replies
-
I'm not sure why there is an NPM release and no GitHub release, but the difference between |
Beta Was this translation helpful? Give feedback.
-
There were no commits for those changes, I literally pulled the packages from npm, bumped the versions manually, and published them to satisfy the auditing tools. We can certainly recreate "commits" retroactively but hope this explains it. |
Beta Was this translation helpful? Give feedback.
-
I was initializing a new project the other day and noticed left-pad among the dependencies. After a bunch of dependency chain tracking, I discovered that it was coming from a [email protected] dependency. [email protected] is the version that resolves from the "^11.5.1" directive for jest-environment-jsdom@^24.9.0. Below, I've included a table of all the dependency changes from [email protected] to [email protected]. I've bolded all of the dependencies where the version in 3.4.1 is higher than the version in 3.4.3. Was this intentional? If so, why?
|
Beta Was this translation helpful? Give feedback.
There were no commits for those changes, I literally pulled the packages from npm, bumped the versions manually, and published them to satisfy the auditing tools. We can certainly recreate "commits" retroactively but hope this explains it.