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

Request for Package Release #21644

Closed
LandonSchropp opened this issue Jun 8, 2021 · 3 comments
Closed

Request for Package Release #21644

LandonSchropp opened this issue Jun 8, 2021 · 3 comments
Labels
Status: Unconfirmed A potential issue that we haven't yet confirmed as a bug

Comments

@LandonSchropp
Copy link

I'm sorry if this is the wrong place to file this, but I wasn't sure how else to get ahold of the React team. The #21392 by @bvaughn fixes an issue that was causing MobX components to display components in stack traces as wrappedComponent, making it very hard to debug issues. This PR was merged back in April, but there hasn't been a React release since March. Is there any chance you guys would be willing to release React 17.0.3 with this fix?

Thanks!

@LandonSchropp LandonSchropp added the Status: Unconfirmed A potential issue that we haven't yet confirmed as a bug label Jun 8, 2021
@gaearon
Copy link
Collaborator

gaearon commented Jun 8, 2021

We’re already pretty deep into preparing the next major. This doesn’t mean a 17 patch is impossible but it’s still a bit of a risk and a distraction that we’d prefer to take only if it’s due to an urgent issue. This is because any fix would have the be cherry-picked (because 17.0.x is far behind the mainline), and cherry-picking always creates some risk as we’ve never run such a build in production ourselves.

I’ll try to keep that PR in mind if we do end up cutting another 17.x release for one reason or another. But it’s probably not enough of a reason by itself to cut a patch at this time. Sorry about that. You can get it in the @next release tag though if you don’t mind using unstable versions (at your own risk).

@bvaughn
Copy link
Contributor

bvaughn commented Jun 8, 2021

I'm going to close this issue since it's a question and Dan has answered it. As Dan mentioned, we probably aren't going to put out a 17 patch release just for this fix because those require a lot of testing and extra processes. If we need to do one for other reasons (bug fixes) we will consider this as well though.

@bvaughn bvaughn closed this as completed Jun 8, 2021
@LandonSchropp
Copy link
Author

That's understandable. I didn't think about using the @next flag. That should meet my debugging needs. Thanks for the response!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Unconfirmed A potential issue that we haven't yet confirmed as a bug
Projects
None yet
Development

No branches or pull requests

3 participants