Do housekeeping + drop support for IE<9 #104
Conversation
|
@leobalter What can I do about the BrowserStack auth error? |
|
Seems pretty good if we can fix the CI fail. |
|
Not that it matters a ton, but I would think that instead of |
I used the component that's in the |
|
I removed the outdated Core patch releases from available versions but I may add them back if you think it's worth it (I know UI tries to include everything). |
|
It looks good, I just have not idea what is happening with browserstack now. |
|
@mgol would you mind to rebase this branch? I believe this should be good now. |
|
yes, as I imagine, it works perfectly. +1 to merge when it's rebased. |
This also changes the version string to be semver-valid.
This makes commands like `npm install package --save-dev` always get saved to package.json as a pinned version and not as a `^`-delimited range. Refs jquery/jquery#6600e2e2b9863dc91601d94541a3808cf3ccc90c
This also fixes a JSHint breakage that would occur on a fresh project after running `npm install && grunt`.
…d ones Also set jQuery 3.1.1 as the default tested version.
It was only needed for IE 6.
|
Rebased. I also modified some middle commits (e.g. the one including jQuery 3.0.0-rc1 now includes 3.0.0 final & 3.1.1 instead). IMO it all makes sense to land as separate commits. WDYT? |
|
GitHub swallowed to the void the comment I sent from email. Yes I agree it makes sense to land with separate commits. |
|
I agree, that's why I asked you to rebate, so I can merge through GitHub I'll merge as soon I get into a computer (currently on my phone) On Monday, October 24, 2016, Michał Gołębiowski notifications@github.com
|
Reviewing individual commits might be easier than the whole.
Fixes #89