build(deps): bump @octokit/plugin-paginate-rest, @octokit/rest, @release-it/conventional-changelog and release-it #149

dependabot · 2025-02-14T19:43:36Z

Bumps @octokit/plugin-paginate-rest to 11.4.2 and updates ancestor dependencies @octokit/plugin-paginate-rest, @octokit/rest, @release-it/conventional-changelog and release-it. These dependencies need to be updated together.

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

Release notes

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

v11.4.2

11.4.2 (2025-02-13)

Bug Fixes

types: add back the pagination keys (#653) (8b8c500), closes #652

v11.4.1

11.4.1 (2025-02-13)

Bug Fixes

mitigate ReDos issues & linting issues (#659) (7d1fade), fixes #657

v11.4.0

11.4.0 (2025-01-08)

Features

new action runner groups endpoints, new code scanning alerts autofix endpoints, new sub-issues endpoints, new private registries enpoints, new code security endpoints, various description updates (#646) (a73883f)

v11.3.6

11.3.6 (2024-11-26)

Bug Fixes

types: bump @octokit/types to improve Deno compatibility (#642) (acb6a6e)

v11.3.5

11.3.5 (2024-09-29)

Bug Fixes

types: improve type extraction for namespaced responses and correct async iterator types (#637) (e95444d)

v11.3.4

11.3.4 (2024-09-27)

Bug Fixes

deps: bump @octokit/types (#636) (b2dc51c)

... (truncated)

Commits

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
d9c1e8f chore(deps): update dependency esbuild to ^0.25.0 (#656)
7ed5627 build(deps-dev): bump vitest and @vitest/coverage-v8 (#655)
4a41307 build: remove @types/fetch-mock (#654)
31f8fe9 build(deps): bump vite from 5.4.6 to 6.0.11 (#651)
bc38852 chore(deps): update vitest monorepo to v3 (major) (#650)
a73883f feat: new action runner groups endpoints, new code scanning alerts autofix en...
Additional commits viewable in compare view

Updates @octokit/rest from 18.12.0 to 21.1.0

Release notes

Sourced from @octokit/rest's releases.

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)

Bug Fixes

update REST endpoints (#428) (7058346)

v21.0.0-beta.3

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

Features

... (truncated)

Commits

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)
c59fcf6 chore(deps): update dependency @octokit/tsconfig to v4 (#464)
2f97e4c build(deps): Bump body-parser and express (#465)
2dec6cc chore(deps): update dependency esbuild to ^0.24.0 (#463)
9a80f06 fix(docs): update to react 18 and latest gatsby deps (#462)
3b5a8e8 chore(deps): update dependency fetch-mock to v11 (#459)
Additional commits viewable in compare view

Updates @release-it/conventional-changelog from 7.0.2 to 10.0.0

Release notes

Sourced from @release-it/conventional-changelog's releases.

Release 10.0.0

Update dependencies + bump engines.node (273c84f)

Release 9.0.4

Add default header (resolves #108) (6197330)

Release 9.0.3

Format (09fdb3e)

fix: use whatBump option (#106) (09aac9e)

Release 9.0.2

Minor refactor for readability (ccdd687)

Format docs (73e212c)

fix: Resolve whatBump is not a function error (#105) (5e0af0c)

Release 9.0.1

Update dependencies (6059558)

fix: Allow whatBump to return undefined to skip versioning (#102) (3301fbe)

Release 9.0.0

Update dependencies (1db67c1)

Add .gitignore file (d9416d7)

Release 9.0.0-next.0

Update docs (deeb133)

Streamline opts (ac72e25)

Doc whatBump (1671544)

Try compact (dc1be68)

Add pkg.pr.new workflow (d978f50)

Migrate to conventional-changelog v6 + conventional-recommended-bump v10 (c4b9886)

Release 8.0.2

Add Node.js 22 to test matrix in CI (619c01c)

Upgrade dependencies (e73df9b)

Release 8.0.2-next.0

Update engines.node (da50daf)

Update some deps (791558d)

fix: handle pre-release version properly (#96) (8680cdf)

Update some dependencies (f3c0bad)

Release 8.0.1

Add EOL at end of file (resolves #76) (545b753)

Release 8.0.0

Drop support for Node.js v16 (2c13bcd)

Migrate conventional-recommended-bump (5c35f93)

Update dependencies (5d127a5)

Update README.md (#77) (06192b4)

Commits

b5d0619 Release 10.0.0
273c84f Update dependencies + bump engines.node
3ea3e56 Release 9.0.4
6197330 Add default header (resolves #108)
f86194d Release 9.0.3
09fdb3e Format
09aac9e fix: use whatBump option (#106)
f07f530 Release 9.0.2
ccdd687 Minor refactor for readability
73e212c Format docs
Additional commits viewable in compare view

Updates release-it from 16.1.3 to 18.1.2

Release notes

Sourced from release-it's releases.

Release 18.1.2

Update dependencies (resolves #1197) (260116baa792db50d962afbd1123cb95381145ae)

Release 18.1.1

Exclude the release commit from the release notes (1cca380951d869bb3c7a8d49ac7af9e6ad5be8bc)

Release 18.1.0

Remove tea.yaml (0b9a212e811e0153964fced8abd7ea32e872f23e)

Add releaseNotes object for Octokit REST API based changelog (29fb5137aef70d30c658217d6e77390cc918639f)

Format docs (69d813b6d56766788507fc5ed2da19ae36cab97a)

Use new releaseNotes feature self (1ec12803f10ec6522f05dee76697e638ff6a436d)

Release 18.1.0 (2c5f298518c4f0457468bd6d0ef4ffa88b0e2993)

Release 18.0.0

429 = alive (93fc47b)

Update engines.node (closes #1182) (162cfc9)

Update readme + changelog (4897f1b)

Update dependencies (3c2b1f2)

Merge branch 'v18' (9c480d8)

Release 18.0.0-next.4

Merge branch 'main' into v18 (e3be6db)

Update dependencies (8d227e4)

fix: pass gitlab options to fetch agent (#1185) (d082178)

GitLab Generic Package Repository for assets (#1189) (54399c9)

Update dependencies (ce7e935)

Merge branch 'main' into v18 (fb54e59)

fix(gitlab): don't set Content-Type header when uploading release assets (#1183) (04a36d2)

Fixed GitBase.getLatestVersion to computed formatted tagTemplate before using it for latestTag computation (#1170) (09d7d1b)

Add git-cliff example (#1176) (b161114)

Move configuration options to existing doc pages + table format, shorten (28213bf)

Add docs for configuration options (#1155) (667cd6a)

Improve docs on Tag Match (#1165) (716b44f)

Update dependencies (e994cf3)

Release 18.0.0-next.3

feat(github): expose github make_latest flag (#1150) (57d2c35)

Update dependencies (f1548b9)

Release 18.0.0-next.2

Upgrade sinon (90acfad)

fix(github-comments): make search query respect 256 character limit (encoded) (#1148) (3cec8e3)

Release 18.0.0-next.1

Update dependencies (d8ebe14)

fix: replace obsolete is-ci library by ci-info library (5a08642)

Release 18.0.0-next.0

Fix prompt.transformer check (64197f9)

yes (47536a9)

... (truncated)

Changelog

Sourced from release-it's changelog.

Changelog

This document lists breaking changes for each major release.

See the GitHub Releases page for detailed changelogs: https://github.com/release-it/release-it/releases

v18 (2025-01-06)

Removed support for Node.js v18.

v17 (2023-11-11)

Removed support for Node.js v16.

v16 (2023-07-05)

Removed support for Node.js v14.

v15 (2022-04-30)

Removed support for Node.js v10 and v12.

Removed support for GitLab v12.4 and lower.

Removed anonymous metrics (and the option to disable it).

Programmatic usage and plugins only through ES Module syntax (import)

Use release-it v14 in legacy environments.

v14 (2020-09-03)

Removed global property from plugins. Use this.config[key] instead.

Removed deprecated npm.access option. Set this in package.json instead.

v13 (2020-03-07)

Dropped support for Node v8

Dropped support for GitLab v11.6 and lower.

Deprecated scripts are removed (in favor of hooks).

Removed deprecated --non-interactive (-n) argument. Use --ci instead.

Removed old %s and [REV_RANGE] syntax in command substitutions. Use ${version} and ${latestTag} instead.

v12 (2019-05-03)

The --follow-tags argument for git push has been moved to the default configuration. This is only a breaking change if git.pushArgs was not empty (it was empty by default).

v11

The custom conventional-changelog increment (e.g. "increment": "conventional:angular") with additional script configuration is replaced with a plugin. Please see

... (truncated)

Commits

897fc31 Release 18.1.2
260116b Update dependencies (resolves #1197)
1c3d7b0 Release 18.1.1
1cca380 Exclude the release commit from the release notes
2c5f298 Release 18.1.0
1ec1280 Use new releaseNotes feature self
69d813b Format docs
29fb513 Add releaseNotes object for Octokit REST API based changelog
0b9a212 Remove tea.yaml
c2f7aab Release 18.0.0
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)
You can disable automated security fix PRs for this repo from the Security Alerts page.

…ase-it/conventional-changelog and release-it Bumps [@octokit/plugin-paginate-rest](https://github.com/octokit/plugin-paginate-rest.js) to 11.4.2 and updates ancestor dependencies [@octokit/plugin-paginate-rest](https://github.com/octokit/plugin-paginate-rest.js), [@octokit/rest](https://github.com/octokit/rest.js), [@release-it/conventional-changelog](https://github.com/release-it/conventional-changelog) and [release-it](https://github.com/release-it/release-it). These dependencies need to be updated together. Updates `@octokit/plugin-paginate-rest` from 2.21.3 to 11.4.2 - [Release notes](https://github.com/octokit/plugin-paginate-rest.js/releases) - [Commits](octokit/plugin-paginate-rest.js@v2.21.3...v11.4.2) Updates `@octokit/rest` from 18.12.0 to 21.1.0 - [Release notes](https://github.com/octokit/rest.js/releases) - [Commits](octokit/rest.js@v18.12.0...v21.1.0) Updates `@release-it/conventional-changelog` from 7.0.2 to 10.0.0 - [Release notes](https://github.com/release-it/conventional-changelog/releases) - [Commits](release-it/conventional-changelog@7.0.2...10.0.0) Updates `release-it` from 16.1.3 to 18.1.2 - [Release notes](https://github.com/release-it/release-it/releases) - [Changelog](https://github.com/release-it/release-it/blob/main/CHANGELOG.md) - [Commits](release-it/release-it@16.1.3...18.1.2) --- updated-dependencies: - dependency-name: "@octokit/plugin-paginate-rest" dependency-type: indirect - dependency-name: "@octokit/rest" dependency-type: direct:production - dependency-name: "@release-it/conventional-changelog" dependency-type: direct:development - dependency-name: release-it dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>

github-actions · 2025-02-14T19:44:34Z

Coverage report

Caution

Test run failed

St.^❔	Category	Percentage	Covered / Total
🟡	Statements	79.9% (-9.27% 🔻)	159/199
🟡	Branches	70% (-15.33% 🔻)	49/70
🟡	Functions	77.08% (-10.42% 🔻)	37/48
🟡	Lines	78.95% (-10.06% 🔻)	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/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-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/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.<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.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/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.<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.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.<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 8703122

dependabot bot added the dependencies Pull requests that update a dependency file label Feb 14, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

build(deps): bump @octokit/plugin-paginate-rest, @octokit/rest, @release-it/conventional-changelog and release-it #149

build(deps): bump @octokit/plugin-paginate-rest, @octokit/rest, @release-it/conventional-changelog and release-it #149

dependabot bot commented on behalf of github Feb 14, 2025

github-actions bot commented Feb 14, 2025

build(deps): bump @octokit/plugin-paginate-rest, @octokit/rest, @release-it/conventional-changelog and release-it #149

Are you sure you want to change the base?

build(deps): bump @octokit/plugin-paginate-rest, @octokit/rest, @release-it/conventional-changelog and release-it #149

Conversation

dependabot bot commented on behalf of github Feb 14, 2025

v11.4.2

11.4.2 (2025-02-13)

Bug Fixes

v11.4.1

11.4.1 (2025-02-13)

Bug Fixes

v11.4.0

11.4.0 (2025-01-08)

Features

v11.3.6

11.3.6 (2024-11-26)

Bug Fixes

v11.3.5

11.3.5 (2024-09-29)

Bug Fixes

v11.3.4

11.3.4 (2024-09-27)

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)

Bug Fixes

v21.0.0-beta.3

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

Features

Release 10.0.0

Release 9.0.4

Release 9.0.3

Release 9.0.2

Release 9.0.1

Release 9.0.0

Release 9.0.0-next.0

Release 8.0.2

Release 8.0.2-next.0

Release 8.0.1

Release 8.0.0

Release 18.1.2

Release 18.1.1

Release 18.1.0

Release 18.0.0

Release 18.0.0-next.4

Release 18.0.0-next.3

Release 18.0.0-next.2

Release 18.0.0-next.1

Release 18.0.0-next.0

Changelog

v18 (2025-01-06)

v17 (2023-11-11)

v16 (2023-07-05)

v15 (2022-04-30)

v14 (2020-09-03)

v13 (2020-03-07)

v12 (2019-05-03)

v11

github-actions bot commented Feb 14, 2025

Coverage report

Test suite run failed