Skip to content
NPM

fix single-chat throw no conversation id exception #55

Sign in to view logs

fix single-chat throw no conversation id exception

fix single-chat throw no conversation id exception #55

Triggered via pull request September 19, 2023 02:16
@leochen-gleochen-g
synchronize #51
baidonghui:main
Status Success
Total duration 3m 41s
Artifacts –

npm.yml

on: pull_request
Matrix: Build
Pack
1m 29s
Pack
Publish
0s
Publish
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Build (ubuntu-latest, 16)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build (macos-latest, 16)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build (windows-latest, 16)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Pack
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/