chore(deps): bump lightship from 6.8.0 to 9.0.3 #764

dependabot · 2025-06-25T07:20:00Z

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)

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

--- updated-dependencies: - dependency-name: lightship dependency-version: 9.0.3 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>

dependabot · 2025-06-25T07:20:00Z

Labels

The following labels could not be found: dependabot. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

…rn/lightship-9.0.3

github-actions · 2025-06-25T11:56:57Z

Coverage report

Caution

Test run failed

St.^❔	Category	Percentage	Covered / Total
🟡	Statements	60.2% (+9.65% 🔼)	829/1377
🔴	Branches	43.32% (+8.04% 🔼)	172/397
🔴	Functions	52.82% (+10.27% 🔼)	159/301
🟡	Lines	60.55% (+9.61% 🔼)	749/1237

Show files with reduced coverage 🔻

St.^❔	File	Statements	Branches	Functions	Lines
🟡	error.ts	64.52% (-12.9% 🔻)	100%	33.33% (-22.22% 🔻)	63.33% (-13.33% 🔻)
🟡	`...` / TeamConfigService.ts	71.3% (-0.45% 🔻)	58.93% (-1.79% 🔻)	69.47% (-1.05% 🔻)	70.1% (-0.52% 🔻)
🔴	utils/manifests.ts	58.82% (-23.53% 🔻)	40% (-30% 🔻)	33.33% (-50% 🔻)	58.82% (-23.53% 🔻)
🔴	authz.ts	44.51% (-41.46% 🔻)	22.81% (-45.61% 🔻)	41.03% (-48.72% 🔻)	45% (-44.29% 🔻)
🔴	utils.ts	44.7% (-15.91% 🔻)	13.11% (-21.31% 🔻)	12.5% (-28.13% 🔻)	43.93% (-17.76% 🔻)
🟡	`...` / RepoService.ts	71.56% (-10.09% 🔻)	68.42% (-5.26% 🔻)	50.98% (-15.69% 🔻)	77.55% (-10.2% 🔻)

Test suite run failed

Failed tests: 0/194. Failed suites: 4/12.

  ● 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/apl-api/apl-api/node_modules/serialize-error/index.js:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){import errorConstructors from './error-constructors.js';
                                                                                      ^^^^^^

    SyntaxError: Cannot use import statement outside a module

       6 | import { initialize } from 'express-openapi'
       7 | import { Server } from 'http'
    >  8 | import { createLightship } from 'lightship'
         | ^
       9 | import logger from 'morgan'
      10 | import path from 'path'
      11 | import { CleanOptions } from 'simple-git'

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1505:14)
      at Object.<anonymous> (node_modules/lightship/dist/cjs/factories/createLightship.js:14:27)
      at Object.<anonymous> (node_modules/lightship/dist/cjs/index.js:4:28)
      at Object.<anonymous> (src/app.ts:8:1)
      at Object.<anonymous> (src/otomi-stack.ts:10:1)
      at Object.<anonymous> (src/otomi-stack.test.ts:12: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/apl-api/apl-api/node_modules/serialize-error/index.js:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){import errorConstructors from './error-constructors.js';
                                                                                      ^^^^^^

    SyntaxError: Cannot use import statement outside a module

       6 | import { initialize } from 'express-openapi'
       7 | import { Server } from 'http'
    >  8 | import { createLightship } from 'lightship'
         | ^
       9 | import logger from 'morgan'
      10 | import path from 'path'
      11 | import { CleanOptions } from 'simple-git'

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1505:14)
      at Object.<anonymous> (node_modules/lightship/dist/cjs/factories/createLightship.js:14:27)
      at Object.<anonymous> (node_modules/lightship/dist/cjs/index.js:4:28)
      at Object.<anonymous> (src/app.ts:8:1)
      at Object.<anonymous> (src/api.authz.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/apl-api/apl-api/node_modules/serialize-error/index.js:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){import errorConstructors from './error-constructors.js';
                                                                                      ^^^^^^

    SyntaxError: Cannot use import statement outside a module

       6 | import { initialize } from 'express-openapi'
       7 | import { Server } from 'http'
    >  8 | import { createLightship } from 'lightship'
         | ^
       9 | import logger from 'morgan'
      10 | import path from 'path'
      11 | import { CleanOptions } from 'simple-git'

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1505:14)
      at Object.<anonymous> (node_modules/lightship/dist/cjs/factories/createLightship.js:14:27)
      at Object.<anonymous> (node_modules/lightship/dist/cjs/index.js:4:28)
      at Object.<anonymous> (src/app.ts:8:1)
      at Object.<anonymous> (src/otomi-stack.ts:10:1)
      at Object.<anonymous> (src/middleware/jwt.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/apl-api/apl-api/node_modules/serialize-error/index.js:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){import errorConstructors from './error-constructors.js';
                                                                                      ^^^^^^

    SyntaxError: Cannot use import statement outside a module

       6 | import { initialize } from 'express-openapi'
       7 | import { Server } from 'http'
    >  8 | import { createLightship } from 'lightship'
         | ^
       9 | import logger from 'morgan'
      10 | import path from 'path'
      11 | import { CleanOptions } from 'simple-git'

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1505:14)
      at Object.<anonymous> (node_modules/lightship/dist/cjs/factories/createLightship.js:14:27)
      at Object.<anonymous> (node_modules/lightship/dist/cjs/index.js:4:28)
      at Object.<anonymous> (src/app.ts:8:1)
      at Object.<anonymous> (src/api.test.ts:4:1)

Report generated by 🧪jest coverage report action from 5a91668

…rn/lightship-9.0.3

chore(deps): bump lightship from 6.8.0 to 9.0.3

7db4a43

--- updated-dependencies: - dependency-name: lightship dependency-version: 9.0.3 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>

dependabot bot added the dependencies Pull requests that update a dependency file label Jun 25, 2025

dependabot bot requested review from dennisvankekem and ferruhcihan as code owners June 25, 2025 07:20

dependabot bot added the dependencies Pull requests that update a dependency file label Jun 25, 2025

github-actions bot approved these changes Jun 25, 2025

View reviewed changes

Merge remote-tracking branch 'origin/main' into dependabot/npm_and_ya…

59338d5

…rn/lightship-9.0.3

svcAPLBot added 3 commits June 25, 2025 14:54

Merge remote-tracking branch 'origin/main' into dependabot/npm_and_ya…

5059969

…rn/lightship-9.0.3

Merge remote-tracking branch 'origin/main' into dependabot/npm_and_ya…

a89a590

…rn/lightship-9.0.3

Merge remote-tracking branch 'origin/main' into dependabot/npm_and_ya…

5a91668

…rn/lightship-9.0.3

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

chore(deps): bump lightship from 6.8.0 to 9.0.3 #764

chore(deps): bump lightship from 6.8.0 to 9.0.3 #764

dependabot bot commented on behalf of github Jun 25, 2025 •

edited

Loading

Uh oh!

dependabot bot commented on behalf of github Jun 25, 2025

Uh oh!

github-actions bot commented Jun 25, 2025 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

chore(deps): bump lightship from 6.8.0 to 9.0.3 #764

Are you sure you want to change the base?

chore(deps): bump lightship from 6.8.0 to 9.0.3 #764

Conversation

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

Uh oh!

Uh oh!

dependabot bot commented on behalf of github Jun 25, 2025

Labels

Uh oh!

github-actions bot commented Jun 25, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Coverage report

Test suite run failed

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

dependabot bot commented on behalf of github Jun 25, 2025 •

edited

Loading

github-actions bot commented Jun 25, 2025 •

edited

Loading