Sakurai/pdf.js
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
pdf.js/.github/workflows/ci.yml

38 lines
750 B
YAML
Raw Normal View History

Switch from Travis CI to GitHub Actions
2020-12-19 22:01:10 +01:00
name: CI
on: [push, pull_request]
chore: Set permissions for GitHub actions Restrict the GitHub token permissions only to the required ones; this way, even if the attackers will succeed in compromising your workflow, they won’t be able to do much. - Included permissions for the action. https://github.com/ossf/scorecard/blob/main/docs/checks.md#token-permissions https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#permissions https://docs.github.com/en/actions/using-jobs/assigning-permissions-to-jobs [Keeping your GitHub Actions and workflows secure Part 1: Preventing pwn requests](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/) Signed-off-by: neilnaveen <42328488+neilnaveen@users.noreply.github.com>
2022-06-09 01:08:19 +00:00
permissions:
contents: read
Switch from Travis CI to GitHub Actions
2020-12-19 22:01:10 +01:00
jobs:
Improve the CI workflow YAML file This makes it consistent with the GitHub Advanced Security file and, more importantly, ensures that all steps have a proper name for better visibility.
2021-07-31 13:29:31 +02:00
test:
name: Test
Switch from Travis CI to GitHub Actions
2020-12-19 22:01:10 +01:00
runs-on: ubuntu-latest
Improve the CI workflow YAML file This makes it consistent with the GitHub Advanced Security file and, more importantly, ensures that all steps have a proper name for better visibility.
2021-07-31 13:29:31 +02:00
Update the GitHub Actions workflows to use the current Node.js LTS version The active LTS version is now based on Node.js version 20, hence let's update the relevant workflows to use that one instead; see https://en.wikipedia.org/wiki/Node.js#Releases Given that we still support Node.js version 18, i.e. the maintenance LTS version, in the PDF.js library we'll keep testing both versions in GitHub Actions to prevent regressions.
2023-10-29 11:58:54 +01:00
strategy:
Also test the latest Node.js version in GitHub Actions Hopefully this will allow us to catch bugs in new Node.js versions earlier, rather than having to wait for bug reports. Given that `CompressionStream` is (currently) only potentially used when saving a *modified* PDF document, which is unlikely to be a common use-case in Node.js environments, let's just disable the affected unit-test for now.
2023-10-29 14:21:13 +01:00
fail-fast: false
Update the GitHub Actions workflows to use the current Node.js LTS version The active LTS version is now based on Node.js version 20, hence let's update the relevant workflows to use that one instead; see https://en.wikipedia.org/wiki/Node.js#Releases Given that we still support Node.js version 18, i.e. the maintenance LTS version, in the PDF.js library we'll keep testing both versions in GitHub Actions to prevent regressions.
2023-10-29 11:58:54 +01:00
matrix:
Also test the latest Node.js version in GitHub Actions Hopefully this will allow us to catch bugs in new Node.js versions earlier, rather than having to wait for bug reports. Given that `CompressionStream` is (currently) only potentially used when saving a *modified* PDF document, which is unlikely to be a common use-case in Node.js environments, let's just disable the affected unit-test for now.
2023-10-29 14:21:13 +01:00
node-version: [18, lts/*, latest]
Update the GitHub Actions workflows to use the current Node.js LTS version The active LTS version is now based on Node.js version 20, hence let's update the relevant workflows to use that one instead; see https://en.wikipedia.org/wiki/Node.js#Releases Given that we still support Node.js version 18, i.e. the maintenance LTS version, in the PDF.js library we'll keep testing both versions in GitHub Actions to prevent regressions.
2023-10-29 11:58:54 +01:00
Switch from Travis CI to GitHub Actions
2020-12-19 22:01:10 +01:00
steps:
Improve the CI workflow YAML file This makes it consistent with the GitHub Advanced Security file and, more importantly, ensures that all steps have a proper name for better visibility.
2021-07-31 13:29:31 +02:00
- name: Checkout repository
Bump actions/checkout from 3 to 4 Bumps [actions/checkout](https://github.com/actions/checkout) from 3 to 4. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](https://github.com/actions/checkout/compare/v3...v4) --- updated-dependencies: - dependency-name: actions/checkout dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
2023-09-04 12:51:59 +00:00
uses: actions/checkout@v4
Include the entire `git` history in the work-flows (issue 16366) Without this change we're not able to correctly determine the version number, please refer to https://github.com/actions/checkout#fetch-all-history-for-all-tags-and-branches
2023-04-28 11:42:19 +02:00
with:
fetch-depth: 0
Improve the CI workflow YAML file This makes it consistent with the GitHub Advanced Security file and, more importantly, ensures that all steps have a proper name for better visibility.
2021-07-31 13:29:31 +02:00
Update the GitHub Actions workflows to use the current Node.js LTS version The active LTS version is now based on Node.js version 20, hence let's update the relevant workflows to use that one instead; see https://en.wikipedia.org/wiki/Node.js#Releases Given that we still support Node.js version 18, i.e. the maintenance LTS version, in the PDF.js library we'll keep testing both versions in GitHub Actions to prevent regressions.
2023-10-29 11:58:54 +01:00
- name: Use Node.js ${{ matrix.node-version }}
Upgrade `setup-node` to version 4 in the GitHub Actions workflows This major version mainly involves not using Node.js 16 internally anymore, which will be end of life on September 11th. This prevents the workflows from using an unsupported version of Node.js as well as deprecation warnings getting printed in the workflow logs. For more information please refer to https://github.com/actions/setup-node/releases/tag/v4.0.0 and https://github.com/actions/setup-node/issues/850.
2023-10-28 21:02:51 +02:00
uses: actions/setup-node@v4
Switch from Travis CI to GitHub Actions
2020-12-19 22:01:10 +01:00
with:
Update the GitHub Actions workflows to use the current Node.js LTS version The active LTS version is now based on Node.js version 20, hence let's update the relevant workflows to use that one instead; see https://en.wikipedia.org/wiki/Node.js#Releases Given that we still support Node.js version 18, i.e. the maintenance LTS version, in the PDF.js library we'll keep testing both versions in GitHub Actions to prevent regressions.
2023-10-29 11:58:54 +01:00
node-version: ${{ matrix.node-version }}
Improve the CI workflow YAML file This makes it consistent with the GitHub Advanced Security file and, more importantly, ensures that all steps have a proper name for better visibility.
2021-07-31 13:29:31 +02:00
- name: Install Gulp
run: npm install -g gulp-cli
- name: Install other dependencies
Don't force-install packages in the CI job anymore In PR #16327 the `eslint-plugin-mozilla` package was updated so we no longer have to force-install packages, and the force-install flags for `npm install` were removed. However, the CI job was missing from this commit, which we fix here. In general force-installing packages shouldn't be necessary unless there are problems with dependencies, which we would like to know about, so especially in the CI job it seems like a good idea to not force-install packages to catch upcoming defects early on. Extends 19526d2322fabd4425688bb7c5504fa9ea015c5c.
2023-04-23 12:40:28 +02:00
run: npm install
Improve the CI workflow YAML file This makes it consistent with the GitHub Advanced Security file and, more importantly, ensures that all steps have a proper name for better visibility.
2021-07-31 13:29:31 +02:00
Clean-up the CI workflow a bit After recent PRs the size and scope of the CI workflow is now reduced, and this patch tries to simplify things further. More specifically we can directly specify the gulp-tasks in the workflow, and thus clean-up the `gulpfile` a tiny bit. Note that this will technically be slower, since the tests are now run in series (rather than in parallel), however `gulp externaltest` runs so quickly that it really won't matter in practice.
2023-11-12 13:41:10 +01:00
- name: Run external tests
run: gulp externaltest
- name: Run CLI unit tests
run: gulp unittestcli
Reference in New Issue Copy Permalink