| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*Authors*
- Checking and updating authors has been migrated
to a custom script in the repo
*Changelog*
- changelogplease is no longer maintained
- generate changelog in markdown for GitHub releases
- generate changelog in HTML for blog posts
- generate contributors list in HTML for blog posts
*dist*
- clone dist repo, copy files, and commit/push
- commit tag with dist files on main branch;
remove dist files from main branch after release
*cdn*
- clone cdn repo, copy files, and commit/push
- create versioned and unversioned copies in cdn/
- generate md5 sums and archives for Google and MSFT
*build*
- implement reproducible builds and verify release builds
* uses the last modified date for the latest commit
* See https://reproducible-builds.org/
- the verify workflow also ensures all files were
properly published to the CDN and npm
*docs*
- the new release workflow is documented at build/release/README.md
*verify*
- use the last modified date of the commit before the tag
- use versioned filenames when checking map files on the CDN
- skip factory and package.json files when verifying CDN
*misc*
- now that we don't need the jquery-release script and
now that we no longer need to build on Node 10, we can
use ESM in all files in the build folder
- limit certain workflows to the main repo (not forks)
- version has been set to the previously released version 3.7.1,
as release-it expects
- release-it added the `preReleaseBase` option and we
now always set it to `1` in the npm script. This is
a noop for stable releases.
- include post-release script to be run manually after a release,
with further steps that should be verified manually
Ref jquery/jquery-release#114
Closes gh-5522
|
|
|
|
| |
Ref gh-5441
|
|
|
|
|
|
|
| |
- also add the ability to pass VERSION in env to test final builds
- adjust sha regex to account for lack of shas
- set the version on the dist package.json
Close gh-5408
|
|
|
| |
Close gh-5400
|
|
|
|
|
|
|
| |
https://github.com/jquery/jquery/commit/763ade6dda092709b36d97491951bcae415d91d1#diff-ba51b2c9ce2527b1f191cb2c210748a4f18cccc38893f7ffe1597fb1d23ce027L72
The above change did not work because makeArchives was
not made to return a Promise
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary of the changes:
* expand `node_smoke_tests` to test the full & slim builds
* run `compare_size` on all built minified files; don't run it anymore on
unminified files where they don't provide lots of value
The main goal of this change is to make it easier to compare sizes of both the
full & slim builds between the `3.x-stable` & `main` branches.
Closes gh-5291
Ref gh-5255
(partially cherry-picked from commit 8be4c0e4f89d6c8f780e5937a0534921d8c7815e)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit removes Sizzle from jQuery, inlining its code & removing obsolete
workarounds where applicable.
The Sizzle AUTHORS.txt file has been merged with the jQuery one - people are
sorted by their first contributions to either of the two repositories.
The main `selector` module can be disabled in favor of `selector-native`
via:
grunt custom:-selector
For backwards compatibility, the legacy `sizzle` alias is also supported (it
will be dropped in jQuery `4.0.0`):
grunt custom:-selector
Sizzle tests have been ported to jQuery ones. Ones that are not compatible
with the `selector-native` module are disabled if the regular selector module
is excluded.
Backwards compatibility is still kept for all `Sizzle` utils - they continue to be
available under `jQuery.find` - but the primary implementation is now attached
directly to jQuery.
Some selector utils shared by `selector` & `selector-native` have been
extracted & deduplicated. `jQuery.text` and `jQuery.isXMLDoc` have been
moved to the `core` module.
The commit reduces the gzipped jQuery size by 851 bytes compared to the
`3.x-stable` branch.
Closes gh-5113
Ref gh-4395
Ref gh-4406
|
| |
|
|
|
|
| |
- Not meant to be used like that anymore
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use a dist README fixture kept in the jQuery repository instead of modifying
an existing one. This makes the jQuery repository the single source of truth
when it comes to jQuery releases and it makes it easier to make changes to
README without worrying how it will affect older jQuery lines.
The commit also ES6ifies build/release.js & build/release/dist.js
Closes gh-4614
(cherry picked from commit 358b769a00c3a09a8ec621b8dcb2d5e31b7da69a)
|
|
|
|
|
|
| |
Closes gh-4578
(cherry-picked from 9b9ed469b43e9fa6e2c752444470ae4c87d03d57)
|
|
|
|
|
|
|
|
|
|
|
| |
So far, only browser-based JS files were required to be in strict mode (in the
function form). This commit adds such a requirement to Node.js scripts where
the global form is preferred. All Node.js scripts in sloppy mode were
converted to strict mode.
Closes gh-4499
(cherry picked from commit bbad821c399da92995a11b88d6684970479d4a9b)
|
|
|
|
|
|
|
|
|
|
|
| |
File `src/core.js` has started erroneously being copied to `dist/` in gh-2981.
Fixes gh-4489
Closes gh-4492
Ref gh-2979
Ref gh-2981
(cherry picked from commit 9a4d980639dd804ad320685a25b8ff4572e3f595)
|
| |
|
|
|
|
|
| |
Fixes gh-3237
Close gh-3533
|
|
|
|
|
|
| |
Use eslint pragmas, fix new errors, etc
Closes gh-3148
|
|
|
|
|
| |
Fixes gh-3094
Close gh-3116
|
|
|
|
|
| |
Fixes gh-2979
Close gh-2981
|
|
|
|
|
| |
Fixes gh-2653
Close gh-2711
|
| |
|
|
|
|
| |
Fixes gh-2056
|
|
|
|
| |
Fixes gh-1940
|
| |
|
| |
|
|
|
|
|
|
| |
Fixes gh-1869
Fixes gh-1673
Fixes gh-2045
|
| |
|
| |
|
|
|
|
| |
Fixes #14915
|
|
|
|
| |
Closes gh-1544
|
| |
|
|
|
|
| |
Closes gh-1479
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Tracked bower dependencies are located at "src/sizzle" and "test/libs".
The source-destination mapping is in the Gruntfile.
When updating a bower dependency, update the version in bower.json, run
`grunt bower`, and then commit the result. When adding a dependency,
update the bowercopy task accordingly.
Fixes #14615.
Closes gh-1452.
|
|
|
|
| |
with a small diff
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Per the discussion here:
https://code.google.com/p/chromium/issues/detail?id=256636
Thanks to the Chrome team for the quick response!
This reverts commit d53ddc90c1f119fb9148a553443ef3fbc3f3cc99.
|
|
|
|
|
| |
Normally we'd avoid doing this on a patch release, but Chrome Canary is
spewing deprecation warnings already and that's generating bug tickets.
|
| |
|
|
|
|
| |
(cherry picked from commit ebc7899ba1ba6e8306066b5bd4d3e14f0d2d8aad)
|
| |
|
| |
|