[release] 20231113

[jiqiang90]

Description

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

Fixes # (issue)

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Checklist

• I have tested locally
• I have performed a self review of my changes
• Updated any relevant documentation
• Linked to any relevant issues
• I have added tests relevant to my changes
• Any dependent changes have been merged and published in downstream modules
• My code is up to date with the base branch
• I have updated relevant changelogs. We suggest using chan

[github-actions]

Coverage report

❌ An unexpected error occurred. For more details, check console

Error: The process '/usr/local/bin/yarn' failed with exit code 1

St.❔	Category	Percentage	Covered / Total
🔴	Statements	0%	0/3452
🔴	Branches	0%	0/53
🔴	Functions	0%	0/53
🔴	Lines	0%	0/3452

Test suite run failed

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

  ● 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/subql-algorand/subql-algorand/node_modules/@subql/node-core/node_modules/axios/index.js:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){import axios from './lib/axios.js';
                                                                                      ^^^^^^

    SyntaxError: Cannot use import statement outside a module

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1728:14)
      at Object.<anonymous> (node_modules/@subql/node-core/node_modules/@subql/common/src/project/readers/github-reader.ts:6:1)
      at Object.<anonymous> (node_modules/@subql/node-core/node_modules/@subql/common/src/project/readers/reader.ts:9:1)
      at Object.<anonymous> (node_modules/@subql/node-core/node_modules/@subql/common/src/project/readers/index.ts:4:1)
      at Object.<anonymous> (node_modules/@subql/node-core/node_modules/@subql/common/src/project/index.ts:6:1)
      at Object.<anonymous> (node_modules/@subql/node-core/node_modules/@subql/common/src/index.ts:6:1)
      at Object.<anonymous> (node_modules/@subql/node-core/src/utils/project.ts:7:1)
      at Object.<anonymous> (node_modules/@subql/node-core/src/utils/index.ts:10:1)
      at Object.<anonymous> (node_modules/@subql/node-core/src/api.service.ts:11:1)
      at Object.<anonymous> (node_modules/@subql/node-core/src/index.ts:6: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/subql-algorand/subql-algorand/node_modules/@subql/node-core/node_modules/axios/index.js:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){import axios from './lib/axios.js';
                                                                                      ^^^^^^

    SyntaxError: Cannot use import statement outside a module

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1728:14)
      at Object.<anonymous> (node_modules/@subql/node-core/node_modules/@subql/common/src/project/readers/github-reader.ts:6:1)
      at Object.<anonymous> (node_modules/@subql/node-core/node_modules/@subql/common/src/project/readers/reader.ts:9:1)
      at Object.<anonymous> (node_modules/@subql/node-core/node_modules/@subql/common/src/project/readers/index.ts:4:1)
      at Object.<anonymous> (node_modules/@subql/node-core/node_modules/@subql/common/src/project/index.ts:6:1)
      at Object.<anonymous> (node_modules/@subql/node-core/node_modules/@subql/common/src/index.ts:6:1)
      at Object.<anonymous> (node_modules/@subql/node-core/src/utils/project.ts:7:1)
      at Object.<anonymous> (node_modules/@subql/node-core/src/utils/index.ts:10:1)
      at Object.<anonymous> (node_modules/@subql/node-core/src/api.service.ts:11:1)
      at Object.<anonymous> (node_modules/@subql/node-core/src/index.ts:6: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/subql-algorand/subql-algorand/node_modules/@subql/node-core/node_modules/axios/index.js:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){import axios from './lib/axios.js';
                                                                                      ^^^^^^

    SyntaxError: Cannot use import statement outside a module

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1728:14)
      at Object.<anonymous> (node_modules/@subql/node-core/node_modules/@subql/common/src/project/readers/github-reader.ts:6:1)
      at Object.<anonymous> (node_modules/@subql/node-core/node_modules/@subql/common/src/project/readers/reader.ts:9:1)
      at Object.<anonymous> (node_modules/@subql/node-core/node_modules/@subql/common/src/project/readers/index.ts:4:1)
      at Object.<anonymous> (node_modules/@subql/node-core/node_modules/@subql/common/src/project/index.ts:6:1)
      at Object.<anonymous> (node_modules/@subql/node-core/node_modules/@subql/common/src/index.ts:6:1)
      at Object.<anonymous> (node_modules/@subql/node-core/src/utils/project.ts:7:1)
      at Object.<anonymous> (node_modules/@subql/node-core/src/utils/index.ts:10:1)
      at Object.<anonymous> (node_modules/@subql/node-core/src/api.service.ts:11:1)
      at Object.<anonymous> (node_modules/@subql/node-core/src/index.ts:6: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/subql-algorand/subql-algorand/node_modules/@subql/node-core/node_modules/axios/index.js:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){import axios from './lib/axios.js';
                                                                                      ^^^^^^

    SyntaxError: Cannot use import statement outside a module

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1728:14)
      at Object.<anonymous> (node_modules/@subql/node-core/node_modules/@subql/common/src/project/readers/github-reader.ts:6:1)
      at Object.<anonymous> (node_modules/@subql/node-core/node_modules/@subql/common/src/project/readers/reader.ts:9:1)
      at Object.<anonymous> (node_modules/@subql/node-core/node_modules/@subql/common/src/project/readers/index.ts:4:1)
      at Object.<anonymous> (node_modules/@subql/node-core/node_modules/@subql/common/src/project/index.ts:6:1)
      at Object.<anonymous> (node_modules/@subql/node-core/node_modules/@subql/common/src/index.ts:6:1)
      at Object.<anonymous> (node_modules/@subql/node-core/src/utils/project.ts:7:1)
      at Object.<anonymous> (node_modules/@subql/node-core/src/utils/index.ts:10:1)
      at Object.<anonymous> (node_modules/@subql/node-core/src/api.service.ts:11:1)
      at Object.<anonymous> (node_modules/@subql/node-core/src/index.ts:6:1)

Report generated by 🧪jest coverage report action from 155e27d

[stwiname]

I think this can be reverted

[stwiname]

Should be a minor version