jQuery 4.1.0
- ID
- 47976
- Status
- summarized
- Published
- 18 Nov 2026, 3:50 AM
- Fetched
- 19 Nov 2026, 3:02 AM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://github.com/jquery/jquery/releases/tag/4.1.0
- Source URL
- https://hnrss.org/best
Summary
- Score
- 6.0
- Created
- 19 Nov 2026, 3:03 AM
- Tags
- Audience
- developersvibe_coders
What happened
jQuery 4.1.0 shipped on 17 Nov alongside jQuery 3.8.0, with the release linking to a blog post titled 'passing the torch'. Concrete changes include a ReDoS fix in identifier matching, decoding invalid escape code points to U+FFFD, a workaround for a Safari 27 regex interpreter bug, dropping getElementsByTagName/ClassName in favour of querySelectorAll, serialization support for form-associated custom elements, and a responseURL field on jqXHR. The release notes also add a new commercial support vendor (TuxCare) and, notably, guidelines for machine-generated contributions.
Why it matters
If any of your code builds a jQuery selector from user input (search boxes, filter strings, URL params feeding $()), the ReDoS fix in identifier matching is the one line here that changes your risk profile — pin to 4.1.0 rather than assuming 4.0 covers it. The new 'guidelines for machine-generated contributions' is the other actionable bit: if you or your agents open PRs against OSS, this is an early example of a major project writing down rules for AI-authored patches, which is a preview of what your own repo CONTRIBUTING file will likely need.
Discussion angle
The release notes quietly add rules for machine-generated contributions — what should those rules actually say, and would your team's review process catch an AI-authored patch that looks clean but skips test coverage?