Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, derberg/npm-dependency-manager-for-your-github-org@1eafd3bf3974f21d395c1abac855cb04b295d570. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Dependency installation failed: Error: Command failed with exit code 1: npm install @asyncapi/[email protected] npm error code EUNSUPPORTEDPROTOCOL npm error Unsupported URL Type "workspace:": workspace:* npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-06-12T12_27_36_525Z-debug-0.log

Dependency installation failed: Error: Command failed with exit code 1: npm install @asyncapi/[email protected] npm error code EUNSUPPORTEDPROTOCOL npm error Unsupported URL Type "workspace:": workspace:* npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-06-12T12_27_41_912Z-debug-0.log

Opening PR failed: GraphqlError: No commits between master and bot/bump-@asyncapi/parser-3.1.0

Dependency installation failed: Error: Command failed with exit code 1: npm install @asyncapi/[email protected] npm warn old lockfile npm warn old lockfile The package-lock.json file was created with an old version of npm, npm warn old lockfile so supplemental metadata must be fetched from the registry. npm warn old lockfile npm warn old lockfile This is a one-time fix-up, please be patient... npm warn old lockfile npm warn old lockfile Could not fetch metadata for @asyncapi/[email protected] @asyncapi/edavisualiser: No matching version found for @asyncapi/[email protected]. npm warn old lockfile at module.exports (/usr/local/lib/node_modules/npm/node_modules/npm-pick-manifest/lib/index.js:209:23) npm warn old lockfile at RegistryFetcher.manifest (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/registry.js:131:54) npm warn old lockfile at async /usr/local/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:734:24 { npm warn old lockfile code: 'ETARGET', npm warn old lockfile type: 'version', npm warn old lockfile wanted: '0.15.1', npm warn old lockfile versions: [ '1.2.0' ], npm warn old lockfile distTags: { latest: '1.2.0' }, npm warn old lockfile defaultTag: 'latest' npm warn old lockfile } npm warn deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful. npm warn deprecated [email protected]: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility npm warn deprecated @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-catch-binding instead. npm warn deprecated @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-numeric-separator instead. npm warn deprecated @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-dynamic-import instead. npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported npm warn deprecated [email protected]: Use your platform's native atob() and btoa() methods instead npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported npm warn deprecated [email protected]: Use your platform's native DOMException instead npm warn deprecated [email protected]: Use your platform's native performance.now() and performance.timeOrigin. npm warn deprecated [email protected]: You or someone you depend on is using Q, the JavaScript Promise library that gave JavaScript developers strong feelings about promises. They can almost certainly migrate to the native JavaScript promise now. Thank you literally everyone for joining me in this bet against the odds. Be excellent to each other. npm warn deprecated npm warn deprecated (For a CapTP with native promises, see @endo/eventual-send and @endo/captp) npm warn deprecated @humanwhocodes/[email protected]: Use @eslint/object-schema instead npm warn deprecated [email protected]: See https://github.com/lydell/source-map-resolve#deprecated npm warn deprecated [email protected]: Please use @jridgewell/sourcemap-codec instead npm warn deprecated [email protected]: This package has been deprecated and is no longer maintained. Please use @rollup/plugin-terser npm warn deprecated [email protected]: It is not compatible with newer versions of GA starting with v4, as long as you are using GAv3 it should be ok, but the package is not longer being maintained npm warn deprecated [email protected]: This

Dependency installation failed: Error: Command failed with exit code 1: npm install @asyncapi/[email protected] npm error code ERESOLVE npm error ERESOLVE could not resolve npm error npm error While resolving: @semantic-release/[email protected] npm error Found: [email protected] npm error node_modules/semantic-release npm error peer semantic-release@">=18.0.0-beta.1" from @semantic-release/[email protected] npm error node_modules/semantic-release/node_modules/@semantic-release/commit-analyzer npm error @semantic-release/commit-analyzer@"^9.0.2" from [email protected] npm error peer semantic-release@">=18.0.0-beta.1" from @semantic-release/[email protected] npm error node_modules/semantic-release/node_modules/@semantic-release/github npm error @semantic-release/github@"^8.0.0" from [email protected] npm error 3 more (@semantic-release/npm, ...) npm error npm error Could not resolve dependency: npm error peer semantic-release@">=16.0.0 <18.0.0" from @semantic-release/[email protected] npm error node_modules/@semantic-release/commit-analyzer npm error dev @semantic-release/commit-analyzer@"^8.0.1" from the root project npm error npm error Conflicting peer dependency: [email protected] npm error node_modules/semantic-release npm error peer semantic-release@">=16.0.0 <18.0.0" from @semantic-release/[email protected] npm error node_modules/@semantic-release/commit-analyzer npm error dev @semantic-release/commit-analyzer@"^8.0.1" from the root project npm error npm error Fix the upstream dependency conflict, or retry npm error this command with --force or --legacy-peer-deps npm error to accept an incorrect (and potentially broken) dependency resolution. npm error npm error npm error For a full report see: npm error /home/runner/.npm/_logs/2024-06-12T12_31_34_622Z-eresolve-report.txt npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-06-12T12_31_34_622Z-debug-0.log