build(deps): bump @octokit/plugin-paginate-rest and @octokit/rest #155

dependabot · 2025-04-15T08:43:52Z

Bumps @octokit/plugin-paginate-rest to 11.6.0 and updates ancestor dependency @octokit/rest. These dependencies need to be updated together.

Updates @octokit/plugin-paginate-rest from 2.21.3 to 11.6.0

Release notes

Sourced from @octokit/plugin-paginate-rest's releases.

v11.6.0

11.6.0 (2025-03-18)

Features

new /orgs/{org}/issue-types, /orgs/{org}/issue-types/{issue_type_id} enpoints (#666) (1f44b54)

v11.5.0

11.5.0 (2025-03-18)

Features

new GET /orgs/{org}/actions/hosted-runners, GET /orgs/{org}/actions/runner-groups/{runner_group_id}/hosted-runners, GET /orgs/{org}/rulesets/{ruleset_id}/history, GET /orgs/{org}/settings/network-configurations, GET /repos/{owner}/{repo}/rulesets/{ruleset_id}/history endpoints (#649) (ef30a05)

v11.4.4-cjs.2

11.4.4-cjs.2 (2025-02-26)

[!IMPORTANT] This is a special release to backport newer changes to CJS and address a ReDos vulnerability

Bug Fixes

deps: update @octokit/plugin-rest-endpoint-methods (2c70eaf)

v11.4.4-cjs.1

11.4.4-cjs.1 (2025-02-26)

[!IMPORTANT] This is a special release to backport newer changes to CJS and address a ReDos vulnerability

Bug Fixes

release: set prerelease flag for correct channel (ce534d9) See octokit/plugin-paginate-rest.js@v11.3.1...v11.4.4-cjs.1 for the full comparision

Reverts

Revert "docs(README): update examples to use ESM (#611)" (1389b71)

Revert "feat: package is now ESM (#596)" (64ba6f4)

Revert "fix(pkg): add default fallback and types export (#612)" (27a8552)

v11.4.3

... (truncated)

Commits

1f44b54 feat: new /orgs/{org}/issue-types, `/orgs/{org}/issue-types/{issue_type_id}...
ef30a05 feat: new GET /orgs/{org}/actions/hosted-runners, `GET /orgs/{org}/actions/...
fbadb74 chore(deps): update dependency prettier to v3.5.3 (#665)
1c297ca chore(deps): update dependency semantic-release-plugin-update-version-in-file...
60d26d9 chore(deps): update dependency prettier to v3.5.2 (#664)
9a51aad fix(types): correct pagination return type for data which is an array (#662)
8b8c500 fix(types): add back the pagination keys (#653)
41876f4 chore(deps): update dependency prettier to v3.5.1 (#658)
7d1fade fix: mitigate ReDos issues & linting issues (#659)
bb6c4f9 Merge commit from fork
Additional commits viewable in compare view

Updates @octokit/rest from 18.12.0 to 21.1.1

Release notes

Sourced from @octokit/rest's releases.

v21.1.1

21.1.1 (2025-02-14)

Bug Fixes

deps: update Octokit dependencies to mitigate ReDos [security] (#484) (ca256c3)

v21.1.0

21.1.0 (2025-01-08)

Features

new endpoints, bump Octokit deps to fix Deno (#477) (908b1c8)

v21.0.2

21.0.2 (2024-08-16)

Bug Fixes

docs: update to react 18 and latest gatsby deps (#462) (9a80f06), closes #216 #230 #460

v21.0.1

21.0.1 (2024-07-17)

Bug Fixes

update deps (#456) (93d5afb)

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)

... (truncated)

Commits

ca256c3 fix(deps): update Octokit dependencies to mitigate ReDos [security] (#484)
e791111 chore(deps): update dependency esbuild to ^0.25.0 (#483)
facaa50 build(deps-dev): Bump vitest and @vitest/coverage-v8 (#481)
8a0c472 chore(deps): update dependency undici to v6.21.1 [security] (#480)
4abc914 chore(deps): update vitest monorepo to v3 (major) (#478)
908b1c8 feat: new endpoints, bump Octokit deps to fix Deno (#477)
751b522 chore(deps): update dependency fetch-mock to v12 (#470)
5ad12fd chore(deps): update dependency @types/node to v22 (#472)
c88980a ci(action): update actions/checkout digest to 11bd719 (#469)
94443df ci(action): update actions/checkout digest to eef6144 (#467)
Additional commits viewable in compare view

You can trigger a rebase of this PR 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)
You can disable automated security fix PRs for this repo from the Security Alerts page.

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

Bumps [@octokit/plugin-paginate-rest](https://github.com/octokit/plugin-paginate-rest.js) to 11.6.0 and updates ancestor dependency [@octokit/rest](https://github.com/octokit/rest.js). These dependencies need to be updated together. Updates `@octokit/plugin-paginate-rest` from 2.21.3 to 11.6.0 - [Release notes](https://github.com/octokit/plugin-paginate-rest.js/releases) - [Commits](octokit/plugin-paginate-rest.js@v2.21.3...v11.6.0) Updates `@octokit/rest` from 18.12.0 to 21.1.1 - [Release notes](https://github.com/octokit/rest.js/releases) - [Commits](octokit/rest.js@v18.12.0...v21.1.1) --- updated-dependencies: - dependency-name: "@octokit/plugin-paginate-rest" dependency-version: 11.6.0 dependency-type: indirect - dependency-name: "@octokit/rest" dependency-version: 21.1.1 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>

github-actions · 2025-04-15T08:44:46Z

Coverage report

Caution

Test run failed

St.^❔	Category	Percentage	Covered / Total
🟡	Statements	79.9% (-9.3% 🔻)	159/199
🟡	Branches	70% (-15.33% 🔻)	49/70
🟡	Functions	77.08% (-10.42% 🔻)	37/48
🟡	Lines	78.95% (-10.1% 🔻)	150/190

Show files with reduced coverage 🔻

St.^❔	File	Statements	Branches	Functions	Lines
🟡	git/git-util.ts	74% (-26% 🔻)	61.9% (-38.1% 🔻)	60% (-40% 🔻)	71.11% (-28.89% 🔻)
🔴	`...` / console-logger-service.ts	57.14% (-28.57% 🔻)	75% (-25% 🔻)	40% (-40% 🔻)	57.14% (-28.57% 🔻)

Test suite run failed

Failed tests: 0/57. Failed suites: 12/18.

  ● 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/git-backporting/git-backporting/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 | import LoggerService from "@bp/service/logger/logger-service";
      2 | import LoggerServiceFactory from "@bp/service/logger/logger-service-factory";
    > 3 | import { Octokit } from "@octokit/rest";
        | ^
      4 |
      5 | /**
      6 |  * Singleton factory class for {Octokit} instance

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1495:14)
      at Object.require (src/service/git/github/octokit-factory.ts:3:1)
      at Object.require (src/service/git/github/github-client.ts:5:1)
      at Object.require (src/service/git/git-client-factory.ts:3:1)
      at Object.require (src/service/configs/pullrequest/pr-configs-parser.ts:6:1)
      at Object.require (src/service/runner/runner.ts:4:1)
      at Object.<anonymous> (test/service/runner/cli-github-runner.test.ts:2:1)

  ● 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/git-backporting/git-backporting/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 | import LoggerService from "@bp/service/logger/logger-service";
      2 | import LoggerServiceFactory from "@bp/service/logger/logger-service-factory";
    > 3 | import { Octokit } from "@octokit/rest";
        | ^
      4 |
      5 | /**
      6 |  * Singleton factory class for {Octokit} instance

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1495:14)
      at Object.require (src/service/git/github/octokit-factory.ts:3:1)
      at Object.require (src/service/git/github/github-client.ts:5:1)
      at Object.require (src/service/git/git-client-factory.ts:3:1)
      at Object.require (src/service/configs/pullrequest/pr-configs-parser.ts:6:1)
      at Object.require (src/service/runner/runner.ts:4:1)
      at Object.<anonymous> (test/service/runner/cli-codeberg-runner.test.ts:2:1)

  ● 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/git-backporting/git-backporting/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 | import LoggerService from "@bp/service/logger/logger-service";
      2 | import LoggerServiceFactory from "@bp/service/logger/logger-service-factory";
    > 3 | import { Octokit } from "@octokit/rest";
        | ^
      4 |
      5 | /**
      6 |  * Singleton factory class for {Octokit} instance

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1495:14)
      at Object.require (src/service/git/github/octokit-factory.ts:3:1)
      at Object.require (src/service/git/github/github-client.ts:5:1)
      at Object.require (src/service/git/git-client-factory.ts:3:1)
      at Object.require (src/service/configs/pullrequest/pr-configs-parser.ts:6:1)
      at Object.require (src/service/runner/runner.ts:4:1)
      at Object.<anonymous> (test/service/runner/gha-github-runner.test.ts:2:1)

  ● 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/git-backporting/git-backporting/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 | import LoggerService from "@bp/service/logger/logger-service";
      2 | import LoggerServiceFactory from "@bp/service/logger/logger-service-factory";
    > 3 | import { Octokit } from "@octokit/rest";
        | ^
      4 |
      5 | /**
      6 |  * Singleton factory class for {Octokit} instance

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1495:14)
      at Object.require (src/service/git/github/octokit-factory.ts:3:1)
      at Object.require (src/service/git/github/github-client.ts:5:1)
      at Object.require (src/service/git/git-client-factory.ts:3:1)
      at Object.require (src/service/configs/pullrequest/pr-configs-parser.ts:6:1)
      at Object.require (src/service/runner/runner.ts:4:1)
      at Object.<anonymous> (test/service/runner/cli-gitlab-runner.test.ts:2:1)

  ● 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/git-backporting/git-backporting/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 | import LoggerService from "@bp/service/logger/logger-service";
      2 | import LoggerServiceFactory from "@bp/service/logger/logger-service-factory";
    > 3 | import { Octokit } from "@octokit/rest";
        | ^
      4 |
      5 | /**
      6 |  * Singleton factory class for {Octokit} instance

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1495:14)
      at Object.require (src/service/git/github/octokit-factory.ts:3:1)
      at Object.require (src/service/git/github/github-client.ts:5:1)
      at Object.require (src/service/git/git-client-factory.ts:3:1)
      at Object.require (src/service/configs/pullrequest/pr-configs-parser.ts:6:1)
      at Object.<anonymous> (test/service/configs/pullrequest/gitlab-pr-configs-parser.test.ts:3:1)

  ● 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/git-backporting/git-backporting/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 | import LoggerService from "@bp/service/logger/logger-service";
      2 | import LoggerServiceFactory from "@bp/service/logger/logger-service-factory";
    > 3 | import { Octokit } from "@octokit/rest";
        | ^
      4 |
      5 | /**
      6 |  * Singleton factory class for {Octokit} instance

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1495:14)
      at Object.require (src/service/git/github/octokit-factory.ts:3:1)
      at Object.require (src/service/git/github/github-client.ts:5:1)
      at Object.require (src/service/git/git-client-factory.ts:3:1)
      at Object.require (src/service/configs/pullrequest/pr-configs-parser.ts:6:1)
      at Object.<anonymous> (test/service/configs/pullrequest/github-pr-configs-parser.test.ts:3:1)

  ● 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/git-backporting/git-backporting/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 | import LoggerService from "@bp/service/logger/logger-service";
      2 | import LoggerServiceFactory from "@bp/service/logger/logger-service-factory";
    > 3 | import { Octokit } from "@octokit/rest";
        | ^
      4 |
      5 | /**
      6 |  * Singleton factory class for {Octokit} instance

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1495:14)
      at Object.require (src/service/git/github/octokit-factory.ts:3:1)
      at Object.require (src/service/git/github/github-client.ts:5:1)
      at Object.require (src/service/git/git-client-factory.ts:3:1)
      at Object.require (src/service/configs/pullrequest/pr-configs-parser.ts:6:1)
      at Object.require (src/service/runner/runner.ts:4:1)
      at Object.<anonymous> (test/service/runner/gha-gitlab-runner.test.ts:2:1)

  ● 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/git-backporting/git-backporting/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 | import LoggerService from "@bp/service/logger/logger-service";
      2 | import LoggerServiceFactory from "@bp/service/logger/logger-service-factory";
    > 3 | import { Octokit } from "@octokit/rest";
        | ^
      4 |
      5 | /**
      6 |  * Singleton factory class for {Octokit} instance

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1495:14)
      at Object.require (src/service/git/github/octokit-factory.ts:3:1)
      at Object.require (src/service/git/github/github-client.ts:5:1)
      at Object.require (src/service/git/git-client-factory.ts:3:1)
      at Object.require (src/service/configs/pullrequest/pr-configs-parser.ts:6:1)
      at Object.<anonymous> (test/service/configs/pullrequest/github-pr-configs-parser-multiple.test.ts:3:1)

  ● 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/git-backporting/git-backporting/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 | import LoggerService from "@bp/service/logger/logger-service";
      2 | import LoggerServiceFactory from "@bp/service/logger/logger-service-factory";
    > 3 | import { Octokit } from "@octokit/rest";
        | ^
      4 |
      5 | /**
      6 |  * Singleton factory class for {Octokit} instance

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1495:14)
      at Object.require (src/service/git/github/octokit-factory.ts:3:1)
      at Object.require (src/service/git/github/github-client.ts:5:1)
      at Object.require (src/service/git/git-client-factory.ts:3:1)
      at Object.<anonymous> (test/service/git/gitlab/gitlab-client.test.ts:1:1)

  ● 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/git-backporting/git-backporting/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 | import LoggerService from "@bp/service/logger/logger-service";
      2 | import LoggerServiceFactory from "@bp/service/logger/logger-service-factory";
    > 3 | import { Octokit } from "@octokit/rest";
        | ^
      4 |
      5 | /**
      6 |  * Singleton factory class for {Octokit} instance

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1495:14)
      at Object.require (src/service/git/github/octokit-factory.ts:3:1)
      at Object.require (src/service/git/github/github-client.ts:5:1)
      at Object.require (src/service/git/git-client-factory.ts:3:1)
      at Object.require (src/service/configs/pullrequest/pr-configs-parser.ts:6:1)
      at Object.<anonymous> (test/service/configs/pullrequest/gitlab-pr-configs-parser-multiple.test.ts:3:1)

  ● 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/git-backporting/git-backporting/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 | import LoggerService from "@bp/service/logger/logger-service";
      2 | import LoggerServiceFactory from "@bp/service/logger/logger-service-factory";
    > 3 | import { Octokit } from "@octokit/rest";
        | ^
      4 |
      5 | /**
      6 |  * Singleton factory class for {Octokit} instance

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1495:14)
      at Object.require (src/service/git/github/octokit-factory.ts:3:1)
      at Object.require (src/service/git/github/github-client.ts:5:1)
      at Object.require (src/service/git/git-client-factory.ts:3:1)
      at Object.<anonymous> (test/service/git/git-client-factory.test.ts:1:1)

  ● 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/git-backporting/git-backporting/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 | import LoggerService from "@bp/service/logger/logger-service";
      2 | import LoggerServiceFactory from "@bp/service/logger/logger-service-factory";
    > 3 | import { Octokit } from "@octokit/rest";
        | ^
      4 |
      5 | /**
      6 |  * Singleton factory class for {Octokit} instance

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1495:14)
      at Object.require (src/service/git/github/octokit-factory.ts:3:1)
      at Object.require (src/service/git/github/github-client.ts:5:1)
      at Object.require (src/service/git/git-client-factory.ts:3:1)
      at Object.<anonymous> (test/service/git/github/github-client.test.ts:1:1)

Report generated by 🧪jest coverage report action from ddb20c0

dependabot · 2025-10-13T10:01:25Z

OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Apr 15, 2025

lampajr closed this Oct 13, 2025

dependabot bot deleted the dependabot/npm_and_yarn/multi-e85ade362c branch October 13, 2025 10:01

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

build(deps): bump @octokit/plugin-paginate-rest and @octokit/rest #155

build(deps): bump @octokit/plugin-paginate-rest and @octokit/rest #155

Uh oh!

dependabot bot commented on behalf of github Apr 15, 2025 •

edited

Loading

Uh oh!

github-actions bot commented Apr 15, 2025

Uh oh!

dependabot bot commented on behalf of github Oct 13, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

build(deps): bump @octokit/plugin-paginate-rest and @octokit/rest #155

build(deps): bump @octokit/plugin-paginate-rest and @octokit/rest #155

Uh oh!

Conversation

dependabot bot commented on behalf of github Apr 15, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

v11.6.0

11.6.0 (2025-03-18)

Features

v11.5.0

11.5.0 (2025-03-18)

Features

v11.4.4-cjs.2

11.4.4-cjs.2 (2025-02-26)

Bug Fixes

v11.4.4-cjs.1

11.4.4-cjs.1 (2025-02-26)

Bug Fixes

Reverts

v11.4.3

v21.1.1

21.1.1 (2025-02-14)

Bug Fixes

v21.1.0

21.1.0 (2025-01-08)

Features

v21.0.2

21.0.2 (2024-08-16)

Bug Fixes

v21.0.1

21.0.1 (2024-07-17)

Bug Fixes

v21.0.0

21.0.0 (2024-06-20)

Features

BREAKING CHANGES

v21.0.0-beta.4

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

Uh oh!

github-actions bot commented Apr 15, 2025

Coverage report

Test suite run failed

Uh oh!

dependabot bot commented on behalf of github Oct 13, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

dependabot bot commented on behalf of github Apr 15, 2025 •

edited

Loading