pdf.js/.github/workflows/ci.yml

name: CI
on: [push, pull_request]
permissions:
  contents: read

jobs:
  test:
    name: Test
    runs-on: ubuntu-latest

    steps:
      - name: Checkout repository
        uses: actions/checkout@v4
        with:
          fetch-depth: 0

      - name: Use Node.js 18 LTS
        uses: actions/setup-node@v3
        with:
          node-version: '18'

      - name: Install Gulp
        run: npm install -g gulp-cli

      - name: Install other dependencies
        run: npm install

      - name: Run tests
        run: gulp ci-test
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
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
Upgrade Node.js to version 18 in the CI workflow Version 16 that we used before is now in maintenance mode, so we should upgrade to the most recent LTS version. For more information on the Node.js release schedule please refer to https://github.com/nodejs/release#release-schedule. 2023-01-08 17:35:08 +01:00			`- name: Use Node.js 18 LTS`
Update GitHub Actions workflow steps to the most recent versions 2022-04-02 15:55:47 +02:00			`uses: actions/setup-node@v3`
Switch from Travis CI to GitHub Actions 2020-12-19 22:01:10 +01:00			`with:`
Upgrade Node.js to version 18 in the CI workflow Version 16 that we used before is now in maintenance mode, so we should upgrade to the most recent LTS version. For more information on the Node.js release schedule please refer to https://github.com/nodejs/release#release-schedule. 2023-01-08 17:35:08 +01:00			`node-version: '18'`
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
			`- name: Run tests`
Remove the `npm test`-command This command was added all the way back when basic CI-support was first introduced (using Travis at the time), however it's never really intended to be used e.g. for local development. By having a `npm test`-command listed in the `package.json` file, there's a very real risk that someone unfamiliar with the code-base would only run that one and thus miss all the other (more important) test-suites[1]. Hence this patch which removes the `npm test`-command, and instead simply calls the relevant gulp-task[2] directly in the GitHub Actions configuration. --- [1] Which consist of the unit-tests (run in browsers), the font-tests (potentially), the reference-tests, and the integration-tests. [2] Which is also renamed slightly, to better fit its current usage. 2021-08-27 16:07:07 +02:00			`run: gulp ci-test`