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

15.6.2 Release Prep #10430

Merged
merged 19 commits into from
Sep 26, 2017
Merged

15.6.2 Release Prep #10430

merged 19 commits into from
Sep 26, 2017

Conversation

nhunzaker
Copy link
Contributor

@nhunzaker nhunzaker commented Aug 10, 2017

Commits

Documentation

  • Changelog
  • Documentation updates

Misc

  • Update lockfile
  • Version bump

@nhunzaker
Copy link
Contributor Author

@aweary @flarnie I think this is good to go, I think the only outstanding tasks beyond deployment are to update the static markup for the website and ship to Bower.

But this PR cherry picks the commits we want (aside from #10025, which we need to figure out) and sets up everything else.

@gaearon
Copy link
Collaborator

gaearon commented Aug 12, 2017

Is anything blocking #10025? I left a comment there: #10025 (comment). I think if that change is made (and code only touches Stack rather than Fiber) then the change is good and we should get it in.

@colebowl
Copy link

@gaearon - It looks like @iansu has done the rebase in issue #10025 and is passing all tests.

@iansu
Copy link
Contributor

iansu commented Aug 14, 2017

I didn't think to comment in this thread. I have reverted the Fiber changes and updated my tests. Everything is passing.

I've been trying not to bug Dan because I think he's on vacation. 😀

@nhunzaker
Copy link
Contributor Author

Awesome. @iansu thanks!

__DEV__ = originalDev;
process.env.NODE_ENV = originalEnv;
}
});
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Controlling for process.env.NODE_ENV is new here. Otherwise, I was unable to get the invariant to minify the warning.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The way it is written here will break other things in non-trivial way. Please check ReactDOMProduction for example of test that overrides process.env.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In fact it would be great if you could send a PR to master that fixes DEV override to work same way as in ReactDOMProduction-test.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It will be done.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay, I've done that in 26722ce and added a TODO to follow up with a similar change on master.

@nhunzaker
Copy link
Contributor Author

Everything checked off. I believe this is good to go.

CHANGELOG.md Outdated
* Prevent event handlers from receiving extra argument (dev only) ([@aweary](https://github.com/aweary) in [#10115](https://github.com/facebook/react/pull/8363)
* Fix cases where onChange would not fire with defaultChecked on radio inputs ([@jquense](https://github.com/jquense) in [#10156](https://github.com/facebook/react/pull/10156))
* Add support for controlList attribute to DOM property whitelist ([@nhunzaker](https://github.com/nhunzaker) in [#9940](https://github.com/facebook/react/pull/9940))
* Fix a bug where creating an element with a ref in a constructor threw an error in dev mode ([@iansu](https://github.com/iansu) in [#10025](https://github.com/facebook/react/pull/10025))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This description is wrong. The bug was that creating an element with a ref in a constructor did NOT throw an error in dev mode.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🙈 Thank you.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got it in da62f42

@colebowl
Copy link

@aweary - Would you be able to complete the requested review?

@iansu - Are there any other steps we need to complete before this can be merged?

@ssilve1989
Copy link

Any update when this will be available? I'm looking to get the fixes for uncontrolled radio buttons.

Copy link
Contributor

@aweary aweary left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, pending the process.env.NODE_ENV stuff @nhunzaker and @gaearon were discussing.

@manikandasankar
Copy link

Any update when this will be available?
I am struck with this issue ChangeEventPlugin.js IE detection is broken

@colebowl
Copy link

colebowl commented Sep 5, 2017

Hi @gaearon / @aweary / @nhunzaker,

I know you guys aren't actively working on this branch as you're working on on the next version but I was wondering if it would be possible to get this wrapped up and merged? There are several folks waiting on this to fix issues in their app (including us).

If there is any more action that needs to be taken, I'd be more than happy take the lead to get this done.

Thanks!

@nhunzaker
Copy link
Contributor Author

@colebowl Thanks for the prod, and I am sorry it was necessary.

I've updated the ref test to use the recommended code and I've updated the timestamps on the changelog and blog post.

This should be good to go, but I'll be out of pocket the rest of the day. I'm happy to review any updates if we need to change anything. I'll circle back later tonight.

@gaearon
Copy link
Collaborator

gaearon commented Sep 25, 2017

We'll need to get the LICENSE change rolled here. Plan to get it out tomorrow.

@sophiebits
Copy link
Collaborator

I can just do it after merging this. Probably easiest that way.

@sophiebits sophiebits merged commit 5634f0d into 15.6-dev Sep 26, 2017
@MichaelDeBoey MichaelDeBoey mentioned this pull request Sep 26, 2017
12 tasks
@gaearon gaearon deleted the 15.6.2-dev branch October 6, 2017 21:57
@nhunzaker nhunzaker mentioned this pull request Nov 16, 2017
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.