Skip to content

chore(release): v3.0.5 (#946) #319

chore(release): v3.0.5 (#946)

chore(release): v3.0.5 (#946) #319

Triggered via push February 4, 2024 10:50
Status Success
Total duration 8m 20s
Artifacts

bump.yml

on: push
Bump this package in repositories that depend on it
8m 11s
Bump this package in repositories that depend on it
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Bump this package in repositories that depend on it
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@26a4f13d740254719971325046822a169aaa7441. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Bump this package in repositories that depend on it
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 @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:119:22) npm WARN old lockfile at async Array.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:727:24) 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:119:22) npm WARN old lockfile at async Array.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:727: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]: 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]: This package has been deprecated and is no longer maintained. Please use @rollup/plugin-terser npm WARN deprecated [email protected]: Use your platform's native atob() and btoa() methods instead 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]: Please use @jridgewell/sourcemap-codec 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-private-methods 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-json-strings 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-class-properties instead. npm WARN deprecated @babel/[email protected]
Bump this package in repositories that depend on it
Dependency installation failed: Error: Command failed with exit code 1: npm install @asyncapi/[email protected] npm ERR! code ERESOLVE npm ERR! ERESOLVE could not resolve npm ERR! npm ERR! While resolving: @semantic-release/[email protected] npm ERR! Found: [email protected] npm ERR! node_modules/semantic-release npm ERR! peer semantic-release@">=18.0.0-beta.1" from @semantic-release/[email protected] npm ERR! node_modules/semantic-release/node_modules/@semantic-release/commit-analyzer npm ERR! @semantic-release/commit-analyzer@"^9.0.2" from [email protected] npm ERR! peer semantic-release@">=18.0.0-beta.1" from @semantic-release/[email protected] npm ERR! node_modules/semantic-release/node_modules/@semantic-release/github npm ERR! @semantic-release/github@"^8.0.0" from [email protected] npm ERR! 3 more (@semantic-release/npm, ...) npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer semantic-release@">=16.0.0 <18.0.0" from @semantic-release/[email protected] npm ERR! node_modules/@semantic-release/commit-analyzer npm ERR! dev @semantic-release/commit-analyzer@"^8.0.1" from the root project npm ERR! npm ERR! Conflicting peer dependency: [email protected] npm ERR! node_modules/semantic-release npm ERR! peer semantic-release@">=16.0.0 <18.0.0" from @semantic-release/[email protected] npm ERR! node_modules/@semantic-release/commit-analyzer npm ERR! dev @semantic-release/commit-analyzer@"^8.0.1" from the root project npm ERR! npm ERR! Fix the upstream dependency conflict, or retry npm ERR! this command with --force or --legacy-peer-deps npm ERR! to accept an incorrect (and potentially broken) dependency resolution. npm ERR! npm ERR! npm ERR! For a full report see: npm ERR! /home/runner/.npm/_logs/2024-02-04T10_54_46_959Z-eresolve-report.txt npm ERR! A complete log of this run can be found in: /home/runner/.npm/_logs/2024-02-04T10_54_46_959Z-debug-0.log
Bump this package in repositories that depend on it
Dependency installation failed: Error: Command failed with exit code 1: npm install @asyncapi/[email protected] npm ERR! code ERESOLVE npm ERR! ERESOLVE could not resolve npm ERR! npm ERR! While resolving: @semantic-release/[email protected] npm ERR! Found: [email protected] npm ERR! node_modules/semantic-release npm ERR! peer semantic-release@">=18.0.0-beta.1" from @semantic-release/[email protected] npm ERR! node_modules/semantic-release/node_modules/@semantic-release/commit-analyzer npm ERR! @semantic-release/commit-analyzer@"^9.0.2" from [email protected] npm ERR! peer semantic-release@">=18.0.0-beta.1" from @semantic-release/[email protected] npm ERR! node_modules/semantic-release/node_modules/@semantic-release/github npm ERR! @semantic-release/github@"^8.0.0" from [email protected] npm ERR! 3 more (@semantic-release/npm, ...) npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer semantic-release@">=16.0.0 <18.0.0" from @semantic-release/[email protected] npm ERR! node_modules/@semantic-release/commit-analyzer npm ERR! dev @semantic-release/commit-analyzer@"^8.0.1" from the root project npm ERR! npm ERR! Conflicting peer dependency: [email protected] npm ERR! node_modules/semantic-release npm ERR! peer semantic-release@">=16.0.0 <18.0.0" from @semantic-release/[email protected] npm ERR! node_modules/@semantic-release/commit-analyzer npm ERR! dev @semantic-release/commit-analyzer@"^8.0.1" from the root project npm ERR! npm ERR! Fix the upstream dependency conflict, or retry npm ERR! this command with --force or --legacy-peer-deps npm ERR! to accept an incorrect (and potentially broken) dependency resolution. npm ERR! npm ERR! npm ERR! For a full report see: npm ERR! /home/runner/.npm/_logs/2024-02-04T10_56_28_000Z-eresolve-report.txt npm ERR! A complete log of this run can be found in: /home/runner/.npm/_logs/2024-02-04T10_56_28_000Z-debug-0.log