Bump @octokit/rest from 20.0.2 to 21.0.0

[dependabot]

Bumps @octokit/rest from 20.0.2 to 21.0.0.

Release notes

Sourced from @​octokit/rest's releases.

v21.0.0

21.0.0 (2024-06-20)

Features

• v21 (#413) (12b6c65)

BREAKING CHANGES

• package is now ESM

v21.0.0-beta.4

21.0.0-beta.4 (2024-06-19)

Bug Fixes

• update REST endpoints (#428) (7058346)

v21.0.0-beta.3

21.0.0-beta.3 (2024-04-30)

Features

• security: Add provenance (#420) (9adf1a4)

v21.0.0-beta.2

21.0.0-beta.2 (2024-04-16)

Bug Fixes

• deps: bump Octokit deps (5d8da12)
• pkg: add a default fallback export (1b6e582)

v21.0.0-beta.1

21.0.0-beta.1 (2024-03-05)

Bug Fixes

• add explicit type anotation (3ddd79e)
• build: adapt for ESM (aad55f4)
• bump deps (21f1aaa)
• deps: bump deps (f179b0b)
• deps: update octokit monorepo (aed67c2)
• docs: update for ESM (42be65a)

... (truncated)

Commits

• 12b6c65 feat: v21 (#413)
• 32649a8 build(deps-dev): Bump braces from 3.0.2 to 3.0.3 (#439)
• 53cee64 ci(action): update actions/checkout digest to 692973e (#438)
• 7c96525 chore(deps): update dependency marked to v13
• a46b4c8 🚧 Workflows have changed (#435)
• b90bc79 chore(deps): update dependency semantic-release to v24
• bc41b70 chore(deps): update dependency esbuild to ^0.21.0 (#429)
• c1892ed ci(action): update actions/checkout digest to a5ac7e5 (#432)
• 7058346 fix: update REST endpoints (#428)
• b4e2102 ci(action): update actions/checkout digest to 0ad4b8f (#426)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[ghaiszaher]

Looks like tests are failing here

[crypticmind]

Looks like tests are failing here

You're right. The build is failing with this error now:

 FAIL ./action.test.js
  ● Test suite failed to run

    Jest encountered an unexpected token

    Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.

    Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.

    By default "node_modules" folder is ignored by transformers.

    Here's what you can do:
     • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it.
     • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

    You'll find more details and examples of these config options in the docs:
    https://jestjs.io/docs/configuration
    For information about custom transformations, see:
    https://jestjs.io/docs/code-transformation

    Details:

    /home/runner/work/action-surefire-report/action-surefire-report/node_modules/@octokit/rest/dist-src/index.js:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){import { Octokit as Core } from "@octokit/core";
                                                                                      ^^^^^^

    SyntaxError: Cannot use import statement outside a module

      1 | const core = require('@actions/core');
      2 | const github = require('@actions/github');
    > 3 | const { Octokit } = require("@octokit/rest");
        |                     ^
      4 | const { retry } = require("@octokit/plugin-retry");
      5 | const RetryingOctokit = Octokit.plugin(retry);
      6 | const { parseTestReports } = require('./utils.js');

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1505:14)
      at Object.require (action.js:3:21)
      at Object.require (action.test.js:4:16)

[dependabot]

Superseded by #221.