library-mirrors/jquery
1
0
Fork 0
mirror of https://github.com/jquery/jquery.git synced 2024-12-09 08:04:24 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
bf11739f6c
jquery/.github/workflows/node.js.yml

86 lines
3.0 KiB
YAML
Raw Normal View History

Build: Migrate CI to GitHub Actions Closes gh-4800
2021-11-30 22:56:39 +00:00
name: CI
Build: Don't run CI push workflows for dependabot branches Without this change, dependabot PRs run double checks - one set for the `push` part and one for the `pull_request` part. Closes gh-5353
2023-11-13 17:18:20 +00:00
on:
pull_request:
push:
branches-ignore: "dependabot/**"
Build: Migrate CI to GitHub Actions Closes gh-4800
2021-11-30 22:56:39 +00:00
Build: Limit permissions for GitHub workflows Add explicit permissions section[^1] to workflows. This is a security best practice because by default workflows run with extended set of permissions[^2] (except from `on: pull_request` from external forks[^3]. By specifying any permission explicitly all others are set to none. By using the principle of least privilege the damage a compromised workflow can do (because of an injection[^4] or compromised third party tool or action) is restricted. It is recommended to have most strict permissions on the top level[^5] and grant write permissions on job level[^6] on a case by case basis. [^1]: https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#permissions [^2]: https://docs.github.com/en/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token [^3]: https://securitylab.github.com/research/github-actions-preventing-pwn-requests/ [^4]: https://securitylab.github.com/research/github-actions-untrusted-input/ [^5]: https://github.com/ossf/scorecard/blob/main/docs/checks.md#token-permissions [^6]: https://docs.github.com/en/actions/using-jobs/assigning-permissions-to-jobs Closes gh-5119
2022-12-01 13:23:17 +00:00
permissions:
contents: read # to fetch code (actions/checkout)
Build: Migrate CI to GitHub Actions Closes gh-4800
2021-11-30 22:56:39 +00:00
jobs:
build:
runs-on: ubuntu-latest
strategy:
fail-fast: false
matrix:
# Node.js 10 is required by jQuery infra
Build: Test on Node 17, update Grunt & `karma-*` packages This adds testing on Node.js 17 in addition to the currently tested 10, 12, 14 and 16 versions. Also, update Grunt & `karma-*` packages. Testing in Karma on jsdom is broken in Node 17 at the moment; until we find a fix, this change disables such testing on Node 17 or newer. Node smoke tests & promises aplus tests are disabled on Node.js 10 as they depend on jsdom and the latest jsdom version doesn't run properly on Node 10. Closes gh-5023
2022-03-14 16:58:41 +00:00
# Do not remove 16.x until jsdom tests are re-enabled on newer Node.js versions.
Build: Test on Node.js 20, stop testing on Node.js 14 & 19 Closes gh-5250
2023-05-22 14:21:35 +00:00
NODE_VERSION: [10.x, 16.x, 18.x, 20.x]
Build: Migrate CI to GitHub Actions Closes gh-4800
2021-11-30 22:56:39 +00:00
NPM_SCRIPT: ["test:browserless"]
include:
Build: Run GitHub Action browser tests on Playwright WebKit So far, we've been running browser tests on GitHub Actions in Chrome and Firefox. Regular Safari is not available in GitHub Actions but Playwright WebKit comes close to a dev version of Safari. With this change, our GitHub CI & local test runs will invoke tests on all actively developed browser engines on all PRs. Also, our GitHub Actions browser tests are now running on Node.js 18. Detection of the Playwright WebKit browser in support unit tests is done by checking if the `test_browser` query parameter is set to `"Playwright"`; this is a `karma-webkit-launcher` feature. Detecting that browser via user agent as we normally do is hard as the UA on Linux is very similar to a real Safari one but it actually uses a newer version of the engine. In addition, we now allow to pass custom browsers when one needs it; e.g., to run the tests in all three engines on Linux/macOS, run: ``` grunt && BROWSERS=ChromeHeadless,FirefoxHeadless,WebkitHeadless grunt karma:main ``` Closes gh-5190
2023-01-23 22:49:44 +00:00
- NAME: "Browser tests: full build, Chrome, Firefox & WebKit"
NODE_VERSION: "18.x"
Build: Migrate CI to GitHub Actions Closes gh-4800
2021-11-30 22:56:39 +00:00
NPM_SCRIPT: "test:browser"
Build: Run GitHub Action browser tests on Playwright WebKit So far, we've been running browser tests on GitHub Actions in Chrome and Firefox. Regular Safari is not available in GitHub Actions but Playwright WebKit comes close to a dev version of Safari. With this change, our GitHub CI & local test runs will invoke tests on all actively developed browser engines on all PRs. Also, our GitHub Actions browser tests are now running on Node.js 18. Detection of the Playwright WebKit browser in support unit tests is done by checking if the `test_browser` query parameter is set to `"Playwright"`; this is a `karma-webkit-launcher` feature. Detecting that browser via user agent as we normally do is hard as the UA on Linux is very similar to a real Safari one but it actually uses a newer version of the engine. In addition, we now allow to pass custom browsers when one needs it; e.g., to run the tests in all three engines on Linux/macOS, run: ``` grunt && BROWSERS=ChromeHeadless,FirefoxHeadless,WebkitHeadless grunt karma:main ``` Closes gh-5190
2023-01-23 22:49:44 +00:00
BROWSERS: "ChromeHeadless,FirefoxHeadless,WebkitHeadless"
- NAME: "Browser tests: slim build, Chrome"
NODE_VERSION: "18.x"
Build: Migrate CI to GitHub Actions Closes gh-4800
2021-11-30 22:56:39 +00:00
NPM_SCRIPT: "test:slim"
BROWSERS: "ChromeHeadless"
Build: Run GitHub Action browser tests on Playwright WebKit So far, we've been running browser tests on GitHub Actions in Chrome and Firefox. Regular Safari is not available in GitHub Actions but Playwright WebKit comes close to a dev version of Safari. With this change, our GitHub CI & local test runs will invoke tests on all actively developed browser engines on all PRs. Also, our GitHub Actions browser tests are now running on Node.js 18. Detection of the Playwright WebKit browser in support unit tests is done by checking if the `test_browser` query parameter is set to `"Playwright"`; this is a `karma-webkit-launcher` feature. Detecting that browser via user agent as we normally do is hard as the UA on Linux is very similar to a real Safari one but it actually uses a newer version of the engine. In addition, we now allow to pass custom browsers when one needs it; e.g., to run the tests in all three engines on Linux/macOS, run: ``` grunt && BROWSERS=ChromeHeadless,FirefoxHeadless,WebkitHeadless grunt karma:main ``` Closes gh-5190
2023-01-23 22:49:44 +00:00
- NAME: "Browser tests: no-deprecated build, Chrome"
NODE_VERSION: "18.x"
Build: Migrate CI to GitHub Actions Closes gh-4800
2021-11-30 22:56:39 +00:00
NPM_SCRIPT: "test:no-deprecated"
BROWSERS: "ChromeHeadless"
Build: Run GitHub Action browser tests on Playwright WebKit So far, we've been running browser tests on GitHub Actions in Chrome and Firefox. Regular Safari is not available in GitHub Actions but Playwright WebKit comes close to a dev version of Safari. With this change, our GitHub CI & local test runs will invoke tests on all actively developed browser engines on all PRs. Also, our GitHub Actions browser tests are now running on Node.js 18. Detection of the Playwright WebKit browser in support unit tests is done by checking if the `test_browser` query parameter is set to `"Playwright"`; this is a `karma-webkit-launcher` feature. Detecting that browser via user agent as we normally do is hard as the UA on Linux is very similar to a real Safari one but it actually uses a newer version of the engine. In addition, we now allow to pass custom browsers when one needs it; e.g., to run the tests in all three engines on Linux/macOS, run: ``` grunt && BROWSERS=ChromeHeadless,FirefoxHeadless,WebkitHeadless grunt karma:main ``` Closes gh-5190
2023-01-23 22:49:44 +00:00
- NAME: "Browser tests: selector-native build, Chrome"
NODE_VERSION: "18.x"
Selector: Re-introduce selector-native.js Re-introduce the `selector-native` similar to the one on the `3.x-stable` branch. One difference is since the `main` branch inlined Sizzle, some selector utils can be shared between the main `selector` module and `selector-native`. The main `selector` module can be disabled in favor of `selector-native` via: grunt custom:-selector Other changes: * Tests: Fix Safari detection - Chrome Headless has a different user agent than Safari and a browser check in selector tests didn't take that into account. * Tests: Run selector-native tests in `npm test` * Selector: Fix querying on document fragments Ref gh-4395 Closes gh-5085
2022-11-21 22:23:39 +00:00
NPM_SCRIPT: "test:selector-native"
BROWSERS: "ChromeHeadless"
Build: Run GitHub Action browser tests on Playwright WebKit So far, we've been running browser tests on GitHub Actions in Chrome and Firefox. Regular Safari is not available in GitHub Actions but Playwright WebKit comes close to a dev version of Safari. With this change, our GitHub CI & local test runs will invoke tests on all actively developed browser engines on all PRs. Also, our GitHub Actions browser tests are now running on Node.js 18. Detection of the Playwright WebKit browser in support unit tests is done by checking if the `test_browser` query parameter is set to `"Playwright"`; this is a `karma-webkit-launcher` feature. Detecting that browser via user agent as we normally do is hard as the UA on Linux is very similar to a real Safari one but it actually uses a newer version of the engine. In addition, we now allow to pass custom browsers when one needs it; e.g., to run the tests in all three engines on Linux/macOS, run: ``` grunt && BROWSERS=ChromeHeadless,FirefoxHeadless,WebkitHeadless grunt karma:main ``` Closes gh-5190
2023-01-23 22:49:44 +00:00
- NAME: "Browser tests: ES modules build, Chrome"
NODE_VERSION: "18.x"
Build: Migrate CI to GitHub Actions Closes gh-4800
2021-11-30 22:56:39 +00:00
NPM_SCRIPT: "test:esmodules"
BROWSERS: "ChromeHeadless"
- NAME: "Browser tests: full build, Firefox ESR"
Build: Run GitHub Action browser tests on Playwright WebKit So far, we've been running browser tests on GitHub Actions in Chrome and Firefox. Regular Safari is not available in GitHub Actions but Playwright WebKit comes close to a dev version of Safari. With this change, our GitHub CI & local test runs will invoke tests on all actively developed browser engines on all PRs. Also, our GitHub Actions browser tests are now running on Node.js 18. Detection of the Playwright WebKit browser in support unit tests is done by checking if the `test_browser` query parameter is set to `"Playwright"`; this is a `karma-webkit-launcher` feature. Detecting that browser via user agent as we normally do is hard as the UA on Linux is very similar to a real Safari one but it actually uses a newer version of the engine. In addition, we now allow to pass custom browsers when one needs it; e.g., to run the tests in all three engines on Linux/macOS, run: ``` grunt && BROWSERS=ChromeHeadless,FirefoxHeadless,WebkitHeadless grunt karma:main ``` Closes gh-5190
2023-01-23 22:49:44 +00:00
NODE_VERSION: "18.x"
Build: Migrate CI to GitHub Actions Closes gh-4800
2021-11-30 22:56:39 +00:00
NPM_SCRIPT: "test:browser"
BROWSERS: "FirefoxHeadless"
steps:
Build: Reformat GitHub workflow Yaml files Use Prettier 3.1.0 to reformat the Yaml files. This makes their format identical to the one used on `3.x-stable`, making for much easier cherry-picks. The main difference is the list under `steps:` was not indented while all other lists were. Closes gh-5364
2023-11-20 17:20:16 +00:00
- name: Checkout
uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1
Build: Migrate CI to GitHub Actions Closes gh-4800
2021-11-30 22:56:39 +00:00
Build: Reformat GitHub workflow Yaml files Use Prettier 3.1.0 to reformat the Yaml files. This makes their format identical to the one used on `3.x-stable`, making for much easier cherry-picks. The main difference is the list under `steps:` was not indented while all other lists were. Closes gh-5364
2023-11-20 17:20:16 +00:00
- name: Cache
Build: Bump actions/cache & github/codeql-action (#5402) * Build: Bump actions/cache from 3.3.2 to 4.0.0 Bumps [actions/cache](https://github.com/actions/cache) from 3.3.2 to 4.0.0. - [Release notes](https://github.com/actions/cache/releases) - [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md) - [Commits](https://github.com/actions/cache/compare/704facf57e6136b1bc63b828d79edcd491f0ee84...13aacd865c20de90d75de3b17ebe84f7a17d57d2) --- updated-dependencies: - dependency-name: actions/cache dependency-type: direct:production update-type: version-update:semver-major ... * Build: Bump github/codeql-action from 3.22.12 to 3.24.0 Bumps [github/codeql-action](https://github.com/github/codeql-action) from 3.22.12 to 3.24.0. - [Release notes](https://github.com/github/codeql-action/releases) - [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md) - [Commits](https://github.com/github/codeql-action/compare/012739e5082ff0c22ca6d6ab32e07c36df03c4a4...e8893c57a1f3a2b659b6b55564fdfdbbd2982911) --- updated-dependencies: - dependency-name: github/codeql-action dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> --------- Closes gh-5402 Closes gh-5415 Signed-off-by: dependabot[bot] <support@github.com>
2024-02-11 00:45:15 +00:00
uses: actions/cache@13aacd865c20de90d75de3b17ebe84f7a17d57d2 # v4.0.0
Build: Reformat GitHub workflow Yaml files Use Prettier 3.1.0 to reformat the Yaml files. This makes their format identical to the one used on `3.x-stable`, making for much easier cherry-picks. The main difference is the list under `steps:` was not indented while all other lists were. Closes gh-5364
2023-11-20 17:20:16 +00:00
with:
path: ~/.npm
key: ${{ runner.os }}-node-${{ matrix.NODE_VERSION }}-npm-lock-${{ hashFiles('**/package-lock.json') }}
restore-keys: |
${{ runner.os }}-node-${{ matrix.NODE_VERSION }}-npm-lock-
Build: Migrate CI to GitHub Actions Closes gh-4800
2021-11-30 22:56:39 +00:00
Build: Reformat GitHub workflow Yaml files Use Prettier 3.1.0 to reformat the Yaml files. This makes their format identical to the one used on `3.x-stable`, making for much easier cherry-picks. The main difference is the list under `steps:` was not indented while all other lists were. Closes gh-5364
2023-11-20 17:20:16 +00:00
- name: Use Node.js ${{ matrix.NODE_VERSION }}
Build: Bump actions/setup-node and github/codeql-action 1: Bump actions/setup-node from 4.0.0 to 4.0.1 Bumps [actions/setup-node](https://github.com/actions/setup-node) from 4.0.0 to 4.0.1. - [Release notes](https://github.com/actions/setup-node/releases) - [Commits](https://github.com/actions/setup-node/compare/8f152de45cc393bb48ce5d89d36b731f54556e65...b39b52d1213e96004bfcb1c61a8a6fa8ab84f3e8) --- updated-dependencies: - dependency-name: actions/setup-node dependency-type: direct:production update-type: version-update:semver-patch ... 2: Bump github/codeql-action from 2.22.5 to 3.22.12 Bumps [github/codeql-action](https://github.com/github/codeql-action) from 2.22.5 to 3.22.12. - [Release notes](https://github.com/github/codeql-action/releases) - [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md) - [Commits](https://github.com/github/codeql-action/compare/74483a38d39275f33fcff5f35b679b5ca4a26a99...012739e5082ff0c22ca6d6ab32e07c36df03c4a4) --- updated-dependencies: - dependency-name: github/codeql-action dependency-type: direct:production update-type: version-update:semver-major ... Closes gh-5381 Closes gh-5382 Signed-off-by: dependabot[bot] <support@github.com>
2024-01-01 00:53:22 +00:00
uses: actions/setup-node@b39b52d1213e96004bfcb1c61a8a6fa8ab84f3e8 # v4.0.1
Build: Reformat GitHub workflow Yaml files Use Prettier 3.1.0 to reformat the Yaml files. This makes their format identical to the one used on `3.x-stable`, making for much easier cherry-picks. The main difference is the list under `steps:` was not indented while all other lists were. Closes gh-5364
2023-11-20 17:20:16 +00:00
with:
node-version: ${{ matrix.NODE_VERSION }}
Build: Migrate CI to GitHub Actions Closes gh-4800
2021-11-30 22:56:39 +00:00
Build: Reformat GitHub workflow Yaml files Use Prettier 3.1.0 to reformat the Yaml files. This makes their format identical to the one used on `3.x-stable`, making for much easier cherry-picks. The main difference is the list under `steps:` was not indented while all other lists were. Closes gh-5364
2023-11-20 17:20:16 +00:00
- name: Install firefox ESR
run: |
export FIREFOX_SOURCE_URL='https://download.mozilla.org/?product=firefox-esr-latest&lang=en-US&os=linux64'
wget --no-verbose $FIREFOX_SOURCE_URL -O - | tar -jx -C ${HOME}
if: contains(matrix.NAME, 'Firefox ESR')
Build: Migrate CI to GitHub Actions Closes gh-4800
2021-11-30 22:56:39 +00:00
Build: Reformat GitHub workflow Yaml files Use Prettier 3.1.0 to reformat the Yaml files. This makes their format identical to the one used on `3.x-stable`, making for much easier cherry-picks. The main difference is the list under `steps:` was not indented while all other lists were. Closes gh-5364
2023-11-20 17:20:16 +00:00
- name: Install dependencies
run: npm install
Build: Separate the install step from running tests in GitHub Actions Also, update the "Run test" label to "Run tests". Closes gh-4992
2022-01-04 15:27:42 +00:00
Build: Reformat GitHub workflow Yaml files Use Prettier 3.1.0 to reformat the Yaml files. This makes their format identical to the one used on `3.x-stable`, making for much easier cherry-picks. The main difference is the list under `steps:` was not indented while all other lists were. Closes gh-5364
2023-11-20 17:20:16 +00:00
- name: Install Playwright dependencies
run: npx playwright-webkit install-deps
if: matrix.NPM_SCRIPT == 'test:browser' && contains(matrix.BROWSERS, 'WebkitHeadless')
Build: migrate most grunt tasks off of grunt Updated tasks include: - lint - npmcopy - build, minify, and process for distribution. - new custom build command using yargs - compare size of minified/gzip built files - pretest scripts, including qunit-fixture, babel transpilation, and npmcopy - node smoke tests - promises aplus tests - new watch task using `rollup.watch` directly Also: - upgraded husky and added the new lint command - updated lint config to use new "flat" config format. See https://eslint.org/docs/latest/use/configure/configuration-files-new - Temporarily disabled one lint rule until flat config is supported by eslint-plugin-import. See https://github.com/import-js/eslint-plugin-import/issues/2556 - committed package-lock.json - updated all test scripts to use the new build - added an express test server that uses middleware-mockserver (this can be used to run tests without karma) - build-all-variants is now build:all Close gh-5318
2023-09-18 16:39:00 +00:00
Build: Reformat GitHub workflow Yaml files Use Prettier 3.1.0 to reformat the Yaml files. This makes their format identical to the one used on `3.x-stable`, making for much easier cherry-picks. The main difference is the list under `steps:` was not indented while all other lists were. Closes gh-5364
2023-11-20 17:20:16 +00:00
- name: Lint code
run: npm run build:all && npm run lint
if: matrix.NODE_VERSION == '18.x'
Build: migrate most grunt tasks off of grunt Updated tasks include: - lint - npmcopy - build, minify, and process for distribution. - new custom build command using yargs - compare size of minified/gzip built files - pretest scripts, including qunit-fixture, babel transpilation, and npmcopy - node smoke tests - promises aplus tests - new watch task using `rollup.watch` directly Also: - upgraded husky and added the new lint command - updated lint config to use new "flat" config format. See https://eslint.org/docs/latest/use/configure/configuration-files-new - Temporarily disabled one lint rule until flat config is supported by eslint-plugin-import. See https://github.com/import-js/eslint-plugin-import/issues/2556 - committed package-lock.json - updated all test scripts to use the new build - added an express test server that uses middleware-mockserver (this can be used to run tests without karma) - build-all-variants is now build:all Close gh-5318
2023-09-18 16:39:00 +00:00
Build: Reformat GitHub workflow Yaml files Use Prettier 3.1.0 to reformat the Yaml files. This makes their format identical to the one used on `3.x-stable`, making for much easier cherry-picks. The main difference is the list under `steps:` was not indented while all other lists were. Closes gh-5364
2023-11-20 17:20:16 +00:00
- name: Run tests
env:
BROWSERS: ${{ matrix.BROWSERS }}
run: |
export PATH=${HOME}/firefox:$PATH
npm run ${{ matrix.NPM_SCRIPT }}
Reference in New Issue Copy Permalink