Skip to content
Bump package version in dependent repos - if Node project

chore(release): v3.4.4 (#1896) #900

Sign in to view logs

chore(release): v3.4.4 (#1896)

chore(release): v3.4.4 (#1896) #900

Triggered via push March 14, 2024 11:25
@asyncapi-botasyncapi-bot
pushed 2b4ce1d
master
Status Success
Total duration 12m 47s
Artifacts –

bump.yml

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

Annotations

3 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 deprecated @types/[email protected]: This is a stub types definition. wrap-ansi provides its own type definitions, so you do not need this installed. npm ERR! code ECONNRESET npm ERR! errno ECONNRESET npm ERR! network Invalid response body while trying to fetch https://registry.npmjs.org/@asyncapi%2fparser: aborted npm ERR! network This is a problem related to network connectivity. npm ERR! network In most cases you are behind a proxy or have bad network settings. npm ERR! network npm ERR! network If you are behind a proxy, please make sure that the npm ERR! network 'proxy' config is set properly. See: 'npm help config' npm ERR! A complete log of this run can be found in: /home/runner/.npm/_logs/2024-03-14T11_36_43_222Z-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-03-14T11_38_40_766Z-eresolve-report.txt npm ERR! A complete log of this run can be found in: /home/runner/.npm/_logs/2024-03-14T11_38_40_766Z-debug-0.log