Potential improperly cut release for v11.1.3 #34139
Labels
bug
Issue was opened via the bug report template.
Comments
|
The 11.1.3@canary releases are what went on to become 12.0.0. The 11.1.3 that was released was just the isolated security patch from 12.0.5 mentioned in the release notes. |
|
@dan-made is correct. |
Merged
|
Thanks all! Really appreciate the clarification 🙏 We'll upgrade to v12 then! Have a wonderful day! |
1 similar comment
This comment was marked as duplicate.
This comment was marked as duplicate.
|
This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Run
next info(available from version 12.0.8 and up)No response
What version of Next.js are you using?
11.1.3
What version of Node.js are you using?
v16
What browser are you using?
Chrome
What operating system are you using?
macOS
How are you deploying your application?
Describe the Bug
Comparing the
v11.1.3-canary.Xtags to what was actually present in the v11.1.3 patch, it looks like numerous commits were omitted from the release. My team was hoping to support node@16 before migrating from next.js v11 to v12 via this commit. Is this code planned to be checked into v11 in the future?Expected Behavior
X
To Reproduce
X
The text was updated successfully, but these errors were encountered: