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.

Sign up for GitHub

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

Jump to bottom

Are jQuery 1.x and 2.x officially end of life? #162

Closed
willc opened this issue May 2, 2017 · 8 comments
Closed

Are jQuery 1.x and 2.x officially end of life? #162

willc opened this issue May 2, 2017 · 8 comments

Comments

@willc
Copy link

willc commented May 2, 2017

I ask, because I can't find any official statement about ongoing patches or maintenance of the 1.x and 2.x series, except for this thread, where it seems to be declared:

jquery/jquery#2432 (comment)

If I interpret that correctly, the identified vulnerability will not get fixed in the 1.x or 2.x series of jQuery, and the official stance is to upgrade to 3.x. Is that correct?
@mgol
Copy link
Member

mgol commented May 2, 2017

Yes, they're EOL. The issue template that appears when you open a new issue at https://github.com/jquery/jquery/issues contains the following text:

Note that we only can fix bugs in the latest version of jQuery.

I assume you'd like to see something on the site as well. Do you have a suggestion where you'd want this info and how it should sound?

If I interpret that correctly, the identified vulnerability will not get fixed in the 1.x or 2.x series of jQuery

We don't give any guarantees for jQuery 1.x/2.x - they're officially unsupported - but if a serious vulnerability was detected (& sent to [email protected]) we might reconsider a patch.

@willc
Copy link
Author

willc commented May 2, 2017

Thanks for the info.

I assume you'd like to see something on the site as well. Do you have a suggestion where you'd want this info and how it should sound?

A blog post or official announcement of some sort would be helpful.

@mgol
Copy link
Member

mgol commented May 2, 2017

cc @timmywil

@timmywil
Copy link
Member

We're going to add a note on the homepage that 1.x and 2.x no longer receive patches.

@willc
Copy link
Author

willc commented Jun 20, 2017

Thanks...looking forward to it.

@MacGyer MacGyer mentioned this issue Jun 23, 2017
Closed
@tomscholz tomscholz mentioned this issue Jul 1, 2017
Closed
@dev-zzo dev-zzo mentioned this issue Jul 3, 2017
Closed
@willc willc mentioned this issue Jul 12, 2017
Closed
@willc
Copy link
Author

willc commented Jul 12, 2017

Just curious for when we can expect this announcement to be made on the homepage.

@mgol
Copy link
Member

mgol commented Jul 12, 2017

A PR is available to review at #163.

@plessbd plessbd mentioned this issue Aug 8, 2017
Closed
4 tasks
@dmethvin
Copy link
Member

Fixed by #163

@jiaola jiaola mentioned this issue Sep 26, 2017
Closed
@JoeBiellik JoeBiellik mentioned this issue Jan 11, 2018
Merged
@boutell boutell mentioned this issue Jan 19, 2018
Closed
@AlekseyMartynov AlekseyMartynov mentioned this issue Jan 22, 2018
Merged
@technopagan technopagan mentioned this issue Mar 25, 2018
Closed
@chillu chillu mentioned this issue Apr 28, 2019
Closed
@jcoyne jcoyne mentioned this issue Aug 7, 2019
Closed
@muxator muxator mentioned this issue Sep 16, 2019
Closed
muxator added a commit to ether/etherpad-lite that referenced this issue Sep 16, 2019
@muxator
jQuery: update vendored version (1.9.1 -> 1.12.4)
5eb60ce 
The vendored jquery version was 1.9.1 from 2013-02-04. Let's replace it with the
most recent one from the 1.x branch (1.12.4 from 2016-05-20).

The modification in rjquery.js is needed because recent jQuery versions changed
their behaviour, and do not set themselves on the global window object.
See: parcel-bundler/parcel#333 (comment)

This will be the lastest jQuery 1.x version ever, because 1.x branch is
definitively EOLed (see jquery/jquery.com#162).

This is a stopgap measure to get the latest security fixes. Going forward,
another strategy will be needed.

Closes #3640
@nyamadori nyamadori mentioned this issue Feb 19, 2020
Open
@Fabian-Schmidt Fabian-Schmidt mentioned this issue Feb 26, 2020
Merged
@willmcb willmcb mentioned this issue Jun 11, 2020
Merged
4 tasks
@tonygermano tonygermano mentioned this issue Jun 16, 2020
Closed
@edg2s edg2s mentioned this issue Jun 18, 2020
Open
@FishHooks FishHooks mentioned this issue Jan 26, 2021
Merged
@gridhead gridhead mentioned this issue Feb 16, 2021
Open
@BoleynSu BoleynSu mentioned this issue May 3, 2021
Closed
@kumbasar kumbasar mentioned this issue Oct 24, 2022
Closed
@reedy reedy mentioned this issue Jun 5, 2023
Open
@Harika19 Harika19 mentioned this issue Oct 11, 2023
Closed
@carolinemichalow carolinemichalow mentioned this issue Oct 24, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@willc @dmethvin @timmywil @mgol